agentleFS
Layneformalized225Layneformalized225/ai-cofounder/skills/user-onboarding/SKILL.md

user-onboarding

Skill1 starsChanged 8 months agoMITView on GitHub

Help users design effective product onboarding. Use when someone is creating first-user experiences, trying to improve activation rates, designing the first 30 seconds of product usage, or working on the path to the aha moment.

9 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.

    line 7
  2. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 9
  3. Distinctive:

    When the user asks for help with user onboarding:

    line 17
  4. Distinctive:

    Understand the aha moment: - Ask what the key value moment is and how quickly users need to reach it

    line 19
  5. Distinctive:

    Apply game design principles: - Use progressive disclosure and reward mechanics from game design

    line 21
  6. Distinctive:

    Connect to retention: - Ensure the onboarding inflects the early user experience toward long-term engagement

    line 22
  7. Distinctive:

    Delaying the aha moment: - Every screen between signup and value is a potential dropoff point

    line 53

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Company Context

Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint. Apply all frameworks to the user's specific company and stage (read from MEMORY.md). Follow output preferences from USER.md (language, format, platform constraints).

User Onboarding

Help the user design effective product onboarding using frameworks and insights from 4 product leaders.

How to Help

When the user asks for help with user onboarding:

  1. Understand the aha moment - Ask what the key value moment is and how quickly users need to reach it
  2. Design the first 30 seconds - Focus intensely on what happens immediately after signup
  3. Apply game design principles - Use progressive disclosure and reward mechanics from game design
  4. Connect to retention - Ensure the onboarding inflects the early user experience toward long-term engagement

Core Principles

Make the first 30 seconds magical

Grant Lee: "We are going to do everything we possibly can to make the first 30 seconds of the product feel magical." The first moments of the user experience are the primary driver for word-of-mouth growth. Invest disproportionately here.

Retention wins come from early experience

Dan Hockenmaier: "Very often I think the biggest wins in retention come from inflecting the early user experience." The onboarding experience is the biggest lever for long-term retention, not just initial activation.

Design from onboarding outward

Merci Grace: "I would design the game from the onboarding experience." Use game design principles where onboarding isn't an afterthought but the foundation from which the rest of the product is built.

Remove blockers to the aha moment

Cam Adams: "We worked a lot on the onboarding process in the last couple of months of launch and that was really pivotal because the product features were there but there was this thing holding people back." Product features may be complete, but invisible friction can prevent users from experiencing them.

Avoid common onboarding anti-patterns

Skip carousels, non-native frameworks, and explanatory screens that don't provide value. Get users into the core product experience as quickly as possible.

Questions to Help Users

  • "What is the single moment where users first experience the core value of your product?"
  • "What happens in the first 30 seconds after a user signs up?"
  • "What friction is between signup and the aha moment, and can any of it be removed?"
  • "Have you watched real users go through onboarding and seen where they struggle?"
  • "How quickly can a user do something meaningful, not just view something?"
  • "What would the onboarding look like if designed like a game tutorial?"

Common Mistakes to Flag

  • Explanation screens instead of action - Users learn by doing, not by reading about doing
  • Delaying the aha moment - Every screen between signup and value is a potential dropoff point
  • Carousels and tooltips - These patterns often indicate the product itself isn't intuitive enough
  • Treating onboarding as separate - Onboarding should be designed as part of the core product, not bolted on
  • Ignoring the first 30 seconds - This is where most users decide whether to invest further

Deep Dive

For all 4 insights from 4 guests, see references/guest-insights.md

Related Skills

  • Measuring Product-Market Fit
  • Designing Growth Loops
  • Retention & Engagement
  • Usability Testing

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.