onboarding-wizard-design
Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates
npx skills add rampstackco/claude-skills --skill onboarding-wizard-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Designs post-signup onboarding wizards that structure the activation path toward the ah-ha moment, using step architecture, progressive disclosure, escape hatches, completion incentives, and drop-off measurement. Emphasizes patterns to avoid tutorial overload and skip-friendly-empty experiences, advocating earned-progressive-disclosure where the right steps appear at the right moments. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, and low activation rates, skipped onboarding leading to non-return, or when audience research indicates missing key features.
How it works
The skill presents a framework for designing the wizard: decide if a wizard is appropriate based on setup steps and multi-action value paths; apply three framing patterns (tutorial-overload, skip-friendly-empty, earned-progressive-disclosure) to determine the approach; outline a step architecture including welcome, identity, critical setup, first-action, configuration deferral, and confirmation steps; plan the ah-ha moment as the visible value demonstration tied to an action within the first session; implement progressive disclosure patterns (default-heavy, required-now, expand-on-demand, branching) to show only what’s needed; specify skip and resume behaviors to avoid landing users in an empty product; establish per-step drop-off measurement and remediation; consider variations by user type (admin vs end-user, technical vs non-technical, team size).
When to use it
Use when scoping a first-run onboarding wizard for the first time, auditing a wizard with poor completion or activation, deciding which features warrant onboarding vs in-product help, or designing the ah-ha moment the wizard is engineered toward. It addresses triggers like activation rates, user skip behavior, and audience research indicating missing features.
What it can touch
Tools and concepts referenced include the post-signup wizard, step architecture, progressive-disclosure patterns, skip-and-resume mechanics, and per-step drop-off instrumentation to guide remediation.
Caveats
The skill notes that wizard maintenance is required to avoid decay; it cautions that skip prominence must be balanced against progress, and that activation rate concerns should center on time-to-value and the ah-ha moment within the first session.
# Onboarding Wizard Design A senior product marketing director's playbook for designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. The discipline of building an onboarding sequence the user actually completes. Most product onboarding wizards fail in one of two ways. They cram every feature into a 12-step intro the user has not earned the patience for. Or they offer a "skip onboarding" button so prominent that users skip into an empty product with no context, and then churn the next day because they never found the value. The activation rate is the metric that matters, and most wizards are optimizing for the wrong thing. The wizards that work do something different. Each step earns the user one step closer to value. The wizard surfaces the right thing at the right moment, not everything upfront. Skip exists but is balanced against staying engaged. The user reaches the ah-ha moment with a sense that the product respected their time. The voice is the senior product marketing director who has watched activation rates double when
- What this skill covers
- The wizard decision: when wizards earn vs when contextual help suffices
- Tutorial-overload vs skip-friendly-empty vs earned-progressive-disclosure
- Step architecture: what belongs in each step, sequence logic
- The ah-ha moment design
- Progressive disclosure patterns
- Skip and resume mechanics
- Drop-off measurement and remediation
- Wizard variations by user type
- Common failure modes
- The framework: 12 considerations for onboarding wizard design
- Reference files
- Closing: wizards earn the user's first session
What does the onboarding-wizard-design skill do?
Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill onboarding-wizard-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.