skills/user-onboarding/SKILL.md
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.
npx skillsauth add cvillamarp-lgtm/skillspodcast user-onboardingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user design effective product onboarding using frameworks and insights from 4 product leaders.
When the user asks for help with user onboarding:
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.
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.
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.
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.
Skip carousels, non-native frameworks, and explanatory screens that don't provide value. Get users into the core product experience as quickly as possible.
For all 4 insights from 4 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.