Design a 14-Screen App Onboarding Flow with One Claude Code Command

Most onboarding flows are written by developers guessing at conversion psychology. The App Onboarding Questionnaire skill flips that: it reads your codebase, applies a documented 14-screen framework, and builds the flow in whatever framework your app already uses. The repo sits at 1,198 stars on the SkillMap leaderboard.

Why This Skill Matters

Onboarding is where subscription apps win or lose users, and the patterns that work are well studied in top apps like Mob, Headspace, Noom, and Duolingo — the four apps the README names as its models. Instead of shipping another generic walkthrough, the skill turns that accumulated playbook into a working implementation: it analyses what your app does, who it is for, and which permissions it needs, then drafts every screen's copy and builds the flow in SwiftUI, React Native, Flutter, or your app's native framework.

Installation

The README offers two install paths. Clone into your Claude Code skills directory:

cd ~/.claude/skills
git clone https://github.com/adamlyttleapps/claude-skill-app-onboarding-questionnaire.git app-onboarding-questionnaire

Note: the README's own clone commands misspell the repo as questoinnaire — the URL above uses the repository's actual spelling.

Alternatively, declare it as a dependency in your project's .claude/settings.json:

{
  "skills": [
    "github:adamlyttleapps/claude-skill-app-onboarding-questionnaire"
  ]
}

Real Workflow: Onboard Users for a Recipe App

1. Open your app's project directory in Claude Code and run the skill's command:

/app-onboarding-questionnaire

2. The skill walks you through each phase interactively. Per the README, it first analyses your codebase to understand what the app does, who it is for, and what permissions it needs.
3. It defines the "user transformation" — the before/after story that drives the onboarding narrative — then designs a screen-by-screen blueprint and drafts all copy: headlines, questions, options, CTAs, and social proof.
4. It builds the onboarding flow in your app's native framework, adapting to your app's complexity. Not every app needs every screen.

The 14-screen framework the README documents: Welcome (hook), Goal Question, Pain Points, Social Proof, Tinder Cards (swipe agree/disagree), Personalised Solution, an optional Comparison Table, Preferences, Permission Priming, a Processing Moment, an App Demo, Value Delivery, an optional Account Gate, and the Paywall.

Two features do the heavy lifting. The App Demo screen builds a functional mini-version of your core loop — users pick recipes or categorise transactions and get a tangible result — and the output is designed to be shareable. Permission Priming auto-detects permissions from your codebase (Info.plist, AndroidManifest) and creates benefit-framed priming screens; the README credits these with converting at 70-80%+ versus roughly 40% for cold system prompts.

Tips

• Progress is resumable: the skill saves state to Claude Code's memory system, so you can return the next day and continue where you left off.
• The framework is based on the README's analysis of the Mob recipe app's 19-screen flow, which the README describes as widely regarded as one of the best-converting onboarding experiences in the App Store.
• Let the codebase analysis run before answering its questions — the permission priming screens depend on what it detects.
• No marketing expertise is required; the skill handles the conversion psychology, you answer questions about your app.

When Not to Use This

The framework targets questionnaire-style onboarding for subscription apps. If your product is a developer tool where users expect to land in the interface immediately, a 14-screen psychological sequence will fight your users' expectations. The skill is also Claude Code-specific — it will not help in a plain chat session.

See the leaderboard for more skills.