onboard

## MANDATORY PREPARATION Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: the "aha moment" you want users to reach, and users' experience level. --- Create or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly. ## Assess Onboarding Needs Understand what users need to learn and why: 1. **Identify the challenge**: - What are users trying to accomplish? - What's confusing or unclear about current experience? - Where do users get stuck or drop off? - What's the "aha moment" we want users to reach? 2. **Understand the users**: - What's their experience level? (Beginners, power users, mixed?) - What's their motivation? (Excited and exploring? Required by work?) - What's their time commitment? (5 minutes? 30 minutes?) - What alternatives do they know? (Coming from competitor? New to category?) 3. **Define success**: - What's the minimum users need to learn to be successful? - What's the key action we want them to take? (First project? First invite?) - How do we know onboarding worked? (Completion rate? Time to value?) **CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible. ## Onboarding Principles Follow these core principles: ### Show, Don't Tell...