Implement and review Apple TipKit feature-discovery UI for iOS 17+ apps. Use when adding or auditing in-app tips, contextual help, coach marks, Tip, TipView, popoverTip, rules, events, actions, display frequency, testing overrides, reusable tip identifiers, or iOS 18+ TipGroup and CloudKit tip sync; avoid for generic SwiftUI navigation or layout outside tip presentation.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use TipKit for small, contextual feature-discovery moments: inline tips, popover tips, rule-gated education, and lightweight coach marks. Keep generic SwiftUI navigation, layout, and long first-run onboarding flows in their sibling skills.
Core TipKit (Tip, TipView, popoverTip, rules, events) is iOS 17+. Gate iOS 18+ APIs (TipGroup, .cloudKitContainer, MaxDisplayDuration) and iOS 26+ APIs (resetEligibility()) explicitly.
Call Tips.configure(_:) once during app startup in init() or application(_:didFinishLaunchingWithOptions:):
import SwiftUI
import TipKit
@main
struct MyApp: App {
init() {
do {
try Tips.configure([
.datastoreLocation(.applicationDefault),
.displayFrequency(.daily)
])
} catch {
assertionFailure("TipKit configuration failed: \(error)")
}
}
var body: some Scene {
WindowGroup { ContentView() }
}
}For app groups sharing tip state, use .groupContainer(identifier:). On iOS 18+, sync tip state across devices by adding .cloudKitContainer(.named("iCloud.com.example.tips")).
Create tips by conforming to the Tip protocol:
struct BookmarkTip: Tip {
var title: Text { Text("Save for Later") }
var message: Text? { Text("Tap to bookmark your favorite articles.") }
var image: Image? { Image(systemName: "bookmark") }
@Parameter
static var hasViewedArticle: Bool = false
static let bookmarkEvent = Event(id: "didBookmarkArticle")
var rules: [Rule] {
#Rule(Self.$hasViewedArticle) { $0 == true }
#Rule(Self.bookmarkEvent) { $0.donations.count < 3 }
}
var actions: [Action] {
Action(id: "learn-more", title: "Learn More") {
// Action handler
}
}
}Present tips inline within layouts or anchored as popovers:
// Inline presentation
TipView(BookmarkTip(), arrowEdge: .bottom)
// Popover presentation anchored to a control
Button("Bookmark", systemImage: "bookmark") {
saveBookmark()
BookmarkTip.bookmarkEvent.donate()
}
.popoverTip(BookmarkTip(), arrowEdge: .top)Invalidate tips when the user completes the taught action: BookmarkTip().invalidate(reason: .actionPerformed).
#Rule(Self.$param)): Persistent state flags representing user characteristics or settings.Event(id:)): Track user interactions. Donate via event.donate(). Use #Rule(event) { $0.donations.count == 0 } for frequency or completion gating.Coordinate multiple tips without cluttering the screen. Store TipGroup in @State:
struct OnboardingView: View {
@State private var tips = TipGroup(.ordered) {
WelcomeTip()
SearchTip()
FilterTip()
}
var body: some View {
VStack {
TipView(tips.currentTip)
ContentView()
}
}
}Use testing overrides only in debug builds, before calling Tips.configure():
#if DEBUG
if ProcessInfo.processInfo.arguments.contains("--reset-tips") {
try? Tips.resetDatastore()
}
if ProcessInfo.processInfo.arguments.contains("--show-all-tips") {
Tips.showAllTipsForTesting()
}
#endif
try Tips.configure()Launch arguments: -com.apple.TipKit.ResetDatastore 1, -com.apple.TipKit.ShowAllTips 1.
Tips.configure() in onAppear races with view layout and can throw datastore errors. Configure in app init().showAllTipsForTesting() bypasses display rules. Keep overrides behind #if DEBUG.TipGroup, .cloudKitContainer, and MaxDisplayDuration with #available(iOS 18, *).id properties, TipKit cannot track persistence and invalidation correctly.Tips.configure(_:) invoked once at app launch before any tip displaysTipGroup, CloudKit container) guarded with availability checksTipGroup stored in @State when sequencing related tipsthienqo/ios-skills
6bf8b62
Canonical home
since May 23, 2026
Also appears in
on Sep 6, 2026
since May 22, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.