Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/onboarding-generator
Generates value-moment-first onboarding flows for iOS/macOS apps — the default architecture races a new user to the first felt experience of the app's promised outcome, branching on whether they can experience it right now or need to plan for later. The classic paged welcome-carousel tour is an explicit fallback for genuinely explain-first apps.
Passed 14 of 22 test cases with the skill, and 8 of 22 without it.
and 8 more in the full report
7 fixed7 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We're noticing high drop-off right after users download our iOS productivity app. Can you help us build a complete SwiftUI onboarding flow for new users on first launch? We need the full set of Swift files for state handling, views for routing new users, and instructions on how to integrate the view swap into our main App structure.
| Checked | Without skill | With skill |
|---|---|---|
| Asks for the app's value moment before outputting fixed code files. | Missed | Passed |
| Recommends a readiness-branching architecture with immediate vs later paths rather than defaulting to a paged carousel. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate onboarding whose job is to get a new user to the value moment — the first time they experience (never just read about) the outcome the app promises — as fast as their situation allows.
Default architecture: value-moment-first, branching on readiness. The user answers one question ("can you do this right now?"), and the path is either the shortest possible route to the value moment, or a captured plan to reach it later. Fallback architecture: the classic paged welcome carousel — generate it only when Step 0 below confirms the app is genuinely explain-first.
Read onboarding-patterns.md for the full philosophy, the nine implementation lessons (each with a code sketch), and a worked case study.
Use this skill when the user:
This is the question that decides every downstream choice — ask it before any configuration question. If the requester can't answer it, help them find it: it's the first specific instant a user feels the outcome, not a feature list. "Sees a demo of X" is not a value moment; "actually did X and saw the result" is.
Onboarding that ends before the user felt the value moment didn't finish — it just stopped.
@Observable needs iOS 17+/macOS 14+; fall back to ObservableObject below that)onboarding-patterns.md Lesson 3)Glob: **/*Paywall*.swift, **/*StoreKit*.swift, or an installed generators/paywall-generator output) — determines free-first vs paywalled-first in Configuration Question 2UNUserNotificationCenter usage already in the project — reuse the existing permission seam if one exists rather than creating a secondGlob: **/*Onboarding*.swift, **/*Welcome*.swift
Grep: "hasCompletedOnboarding" or "isFirstLaunch" or "onboardingCompleted"
If found, ask the user:
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.