user-onboarding

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill user-onboarding
0 commentsdiscussion
summary

Design product onboarding that gets users to their aha moment in the first 30 seconds.

  • Focus intensely on the immediate post-signup experience as the primary driver of word-of-mouth growth and long-term retention
  • Remove friction between signup and core value by identifying and eliminating invisible blockers that prevent users from experiencing product features
  • Apply game design principles like progressive disclosure and reward mechanics to guide users toward meaningful action rather
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
how to use user-onboarding

How to use user-onboarding on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add user-onboarding
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill user-onboarding

The skills CLI fetches user-onboarding from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/user-onboarding

Reload or restart Cursor to activate user-onboarding. Access the skill through slash commands (e.g., /user-onboarding) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.547 reviews
  • Pratham Ware· Dec 16, 2024

    user-onboarding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Carlos Jackson· Dec 16, 2024

    user-onboarding fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Kofi Kim· Dec 12, 2024

    We added user-onboarding from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Chen Jackson· Dec 4, 2024

    I recommend user-onboarding for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kofi Rao· Nov 23, 2024

    Solid pick for teams standardizing on skills: user-onboarding is focused, and the summary matches what you get after install.

  • Charlotte Dixit· Nov 23, 2024

    user-onboarding reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Michael Malhotra· Nov 15, 2024

    user-onboarding has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sakshi Patil· Nov 7, 2024

    user-onboarding is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Layla Gill· Nov 7, 2024

    user-onboarding is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chaitanya Patil· Oct 26, 2024

    Keeps context tight: user-onboarding is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 47

1 / 5