agentleFS
douincdouinc/agent-skills/skills/onboarding-design/SKILL.md

onboarding-design

Skill1 starsChanged 5 months agoMITView on GitHub

Use when designing, reviewing, or auditing signup flows, goal-selection quizzes, permission prompts, paywalls, or any screen a user sees before their first meaningful action.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never list features. Show what the user's life looks like after using the product.

    line 32
  2. Distinctive:

    Every headline must describe a user outcome, not a product capability.

    line 40
  3. Distinctive:

    Never show a generic welcome screen to a user who has already told you their goal.

    line 59
  4. Distinctive:

    Never trigger a native permission dialog without first explaining the benefit.

    line 80
  5. Distinctive:

    Use first-person framing for the confirm action: "I want to stay on track."

    line 89
  6. Distinctive:

    After the quiz, make personalization feel tangible before revealing the paywall:

    line 112

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Onboarding Design

Overview

Onboarding is the product's job interview. Focus every decision on the shortest path to the aha moment: the first instant the user feels the core value personally.

When to Use

Use when:

  • Designing or reviewing signup flows, welcome screens, or goal-selection quizzes
  • Auditing permission prompt placement or copy
  • Building or optimizing a paywall within an onboarding sequence
  • Evaluating any screen between first launch and the user's first meaningful action

Not for:

  • Post-onboarding retention or engagement loops
  • General UX copywriting outside the onboarding context

Core Principles

1. Outcomes Over Features

Never list features. Show what the user's life looks like after using the product.

Instead ofWrite
"Learn vocabulary and grammar""Have real conversations in Paris"
"Track your calories""Fit into those jeans by August"
"Organize your tasks""Leave work on time, every day"

Every headline must describe a user outcome, not a product capability.

2. Drive to the Aha Moment

Identify your product's aha moment first. Every screen audit should start with this answer.

Map every screen between signup and the aha moment. Delete anything that doesn't move the user closer to it.

  • Airbnb: first booking confirmation
  • Spotify: first song played from a personalized playlist
  • Duolingo: first lesson completed with a streak started

3. Personalization First

Collect the user's goal before showing anything generic. Use their answer to:

  • Reorder feature highlights
  • Drive paywall copy and plan recommendation
  • Set the initial dashboard state

Never show a generic welcome screen to a user who has already told you their goal.

4. Delightful Friction

Short onboarding is not always better. Duolingo's 60-screen flow outperforms shorter ones because each screen delivers micro-progress and builds commitment. Delight through:

  • Progress indicators — show steps completed, not steps remaining
  • Loading animations — "Analyzing your answers..." frames waiting as personalization work
  • Micro-copy that celebrates — "Nice! 3 of 5 done"

Replace every neutral transition screen with one that celebrates progress or sets expectations.

5. Human Touch

At least one screen before the paywall must feel like it came from a person:

  • Founder photo or short video on the welcome screen
  • "Written by [Name], CEO" attribution on value propositions
  • Handwritten-style typography for personal messages

6. Pre-Permission Screens

Never trigger a native permission dialog without first explaining the benefit.

Custom screen: "We'll send daily streaks so you never lose progress."
    [I want to stay on track]    [Not now]
         ↓
    Native OS dialog

Use first-person framing for the confirm action: "I want to stay on track."

7. Multi-Intent Support

Users have more than one goal. Allow multiple selections (Headspace model), rank them to infer primary intent, and use the full combination for downstream personalization — not just the first pick.

Monetization

Personalized Paywall

The highest-converting paywall copy references what the user just told you.

Quiz: "What is your main goal?" → "Lose weight"

Paywall: "Your personalized weight-loss plan is ready.
          Most users with your goal reach their target in 8 weeks."

Grammarly's personalized approach produced a 20% lift in upgrade rates over generic copy. The paywall must contain at least one sentence referencing the user's specific quiz answer.

Unlock Value Animation

After the quiz, make personalization feel tangible before revealing the paywall:

"Building your plan..."
[Progress bar fills]
[✓ Goal identified  ✓ Schedule optimized  ✓ Plan ready]
"Your 8-week plan is ready."

Audit Checklist

  • Every headline describes a user outcome (not a feature)
  • The aha moment is identified and all screens before it are justified
  • Quiz answers drive subsequent screen content
  • Progress indicators show completion, not remaining steps
  • Every native permission has a pre-permission screen first
  • Goal/intent questions allow multiple selections
  • The paywall references the user's specific quiz answer
  • An unlock value animation appears between quiz and paywall
  • At least one screen has a human touch element

Common Mistakes

MistakeFix
Feature carousel at launchOutcome-focused value screens
Single-choice goal selectorMulti-select with ranking
Native permission dialog with no contextPre-permission screen first
Generic paywall copyReference quiz answers in headline
Progress bar showing steps remainingShow steps completed
Long form before any valueDeliver one value moment before data collection
Quiz results shown directly as paywallAdd unlock value animation between quiz and paywall

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.