Skip to main content
ClaudeWave
Skill1k repo starsupdated 4mo ago

user-onboarding

This Claude Code skill helps product teams design effective user onboarding experiences by applying frameworks from established product leaders. Use it when designing first-user experiences, improving activation rates, optimizing the critical first 30 seconds after signup, or creating pathways to the aha moment. The skill emphasizes making initial interactions magical, removing friction between signup and core value discovery, and building onboarding as the foundation for long-term retention rather than a separate feature.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/user-onboarding && cp -r /tmp/user-onboarding/skills/user-onboarding ~/.claude/skills/user-onboarding
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# 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
ai-evalsSkill

Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.

ai-product-strategySkill

Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.

analyzing-user-feedbackSkill

Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.

behavioral-product-designSkill

Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.

brand-storytellingSkill

Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.

building-a-promotion-caseSkill

Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.

building-sales-teamSkill

Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.

building-team-cultureSkill

Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.