How do I install the Tipkit skill?

Run npx skillmds@latest add caglarbaranbora/tipkit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tipkit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tipkit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tipkit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tipkit?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tipkit by caglarbaranbora — Agent Skill

Name: Tipkit
Author: caglarbaranbora

Tipkit

Route TipKit implementation tasks to the correct Knowledge Contracts -- tip declaration and content, display rules and event triggers, tip options and app configuration, and presenting tips/tip groups. Use when conforming a struct to Tip, setting title/message/image/actions, writing

File contents

TipKit — Foundations Skill

Purpose

Route TipKit implementation tasks to the minimum required TipKit Knowledge Contracts. v1 scope is in-app feature tips and onboarding hints on iOS 17+ -- declaring tip content, gating display with rules and donated events, one-time app configuration plus per-tip options, and presenting/grouping/dismissing tips -- not custom TipViewStyle authoring, not watchOS-specific presentation differences, and not CloudKit sync of the tip datastore.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/tipkit/.

Conforming a struct to Tip; implementing title/message/image; adding buttons via actions/Tip.Action -> tip-declaration-and-content.md
Writing the rules property with the #Rule(_:) macro over a Tips.Parameter-wrapped variable or a Tips.Event; donating with sendDonation(_:)/donate(); combining multiple rules -> display-rules-and-event-triggers.md
Calling Tips.configure(_:) at app launch; datastoreLocation(_:)/displayFrequency(_:); per-tip options (MaxDisplayCount, MaxDisplayDuration, IgnoresDisplayFrequency) -> tip-options-and-app-configuration.md
Presenting with TipView/popoverTip(_:arrowEdge:action:)/TipUIView/TipUIPopoverViewController; grouping with TipGroup; dismissing with invalidate(reason:)/Tip.InvalidationReason -> presenting-tips-and-tip-groups.md

Never load more than the contracts relevant to the specific question.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/tipkit/ — do not guess or fall back to general knowledge. Custom TipViewStyle/TipViewStyleConfiguration authoring beyond the system default style is out of scope entirely -- not yet built. watchOS-specific TipKit presentation differences are out of scope entirely. Tips.ConfigurationOption.cloudKitContainer(_:) and any cross-device sync of the tip datastore are out of scope entirely -- this is a real, documented TipKit capability (TipKit's datastore does not sync by default, but can be configured to), not a fabricated exclusion; report that boundary explicitly rather than routing to a contract here.

---name: tipkitdescription: Route TipKit implementation tasks to the correct Knowledge Contracts -- tip declaration and content, display rules and event triggers, tip options and app configuration, and presenting tips/tip groups. Use when conforming a struct to Tip, setting title/message/image/actions, writing---# TipKit — Foundations Skill## PurposeRoute TipKit implementation tasks to the minimum required TipKitKnowledge Contracts. v1 scope is in-app feature tips and onboarding hintson iOS 17+ -- declaring tip content, gating display with rules anddonated events, one-time app configuration plus per-tip options, andpresenting/grouping/dismissing tips -- not custom `TipViewStyle`authoring, not watchOS-specific presentation differences, and notCloudKit sync of the tip datastore.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/tipkit/.- Conforming a `struct` to `Tip`; implementing `title`/`message`/`image`; adding buttons via `actions`/`Tip.Action` -> tip-declaration-and-content.md- Writing the `rules` property with the `#Rule(_:)` macro over a `Tips.Parameter`-wrapped variable or a `Tips.Event`; donating with `sendDonation(_:)`/`donate()`; combining multiple rules -> display-rules-and-event-triggers.md- Calling `Tips.configure(_:)` at app launch; `datastoreLocation(_:)`/`displayFrequency(_:)`; per-tip `options` (`MaxDisplayCount`, `MaxDisplayDuration`, `IgnoresDisplayFrequency`) -> tip-options-and-app-configuration.md- Presenting with `TipView`/`popoverTip(_:arrowEdge:action:)`/`TipUIView`/`TipUIPopoverViewController`; grouping with `TipGroup`; dismissing with `invalidate(reason:)`/`Tip.InvalidationReason` -> presenting-tips-and-tip-groups.mdNever load more than the contracts relevant to the specific question.## Stop ConditionsStop and report if the requested topic has no matching KnowledgeContract in knowledge/tipkit/ — do not guess or fall back to generalknowledge. Custom `TipViewStyle`/`TipViewStyleConfiguration` authoringbeyond the system default style is out of scope entirely -- not yetbuilt. watchOS-specific TipKit presentation differences are out ofscope entirely. `Tips.ConfigurationOption.cloudKitContainer(_:)` and anycross-device sync of the tip datastore are out of scope entirely --this is a real, documented TipKit capability (TipKit's datastore doesnot sync by default, but can be configured to), not a fabricatedexclusion; report that boundary explicitly rather than routing to acontract here.

Frequently asked questions