accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design, improve, or audit a post-signup activation flow to get new users to their first value moment. Activate when activation is lagging, time-to-value feels excessive, or first sessions lack impact.
$ npx -y skills add shawnpang/startup-founder-skills --skill onboarding-flow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/onboarding-flowContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user needs to design, improve, or audit a post-signup activation flow to get new users to their first value moment. Activate when activation is lagging, time-to-value feels excessive, or first sessions lack impact.
name: onboarding-flow description: When the user needs to design, improve, or audit a post-signup activation flow to get new users to their first value moment. Activate when activation is lagging, time-to-value feels excessive, or first sessions lack impact. related: [support-docs, email-marketing, churn-analysis] reads: [startup-context]
Activate when a founder or product lead needs to design onboarding for new users, improve activation rates, reduce time-to-value, fix drop-off after signup, redesign a guided setup experience, or re-engage users who stalled during onboarding. This includes prompts like "design our onboarding flow," "users are dropping off after signup," "build an activation checklist," "our time-to-value is too long," "how do we get users to their aha moment faster," or "first sessions are not sticking."
Do NOT use for employee onboarding, service process design, or when the product lacks a stable value proposition. This skill is for in-product user activation only.
1. **Intake and goal-framing** — Read startup-context if available. Establish the activation goal, current baseline metrics, and what success looks like. If the user does not know their activation event, help them hypothesize based on product type (see benchmarks below). 2. **Map the current journey** — Document every step from signup to activation event, including screens, emails, wait states, and decision points. Identify friction points, unnecessary steps, and moments of confusion. 3. **Identify friction and drop-off** — Pinpoint where users abandon the flow. Categorize blockers: too many steps, unclear value, technical obstacles, cognitive overload, or missing guidance. 4. **Define behavioral activation moments** — Identify the specific user actions that predict long-term retention. These become the milestones the onboarding flow drives toward. 5. **Design the first experience** — Apply the progressive onboarding framework to restructure the journey. Focus on the "first 30 seconds" experience and minimize steps before first value. Defer non-essential setup. 6. **Build the milestone-based onboarding plan** — Create a "first mile" plan with clear milestones from signup through habit formation, with coordinated in-app and email touchpoints. 7. **Establish measurement and experiments** — Set up tracking for each step in the funnel. Build an experiment backlog prioritized by impact, confidence, and effort. Design A/B tests for the highest-leverage changes.
A comprehensive Onboarding & Activation Pack including: 1. **Activation spec** — Defined activation event with behavioral criteria and baseline metrics 2. **First 30 seconds design** — The immediate post-signup experience optimized for first value 3. **First mile milestone plan** — Stage-by-stage plan from signup through habit formation 4. **Funnel map** — Every step with expected conversion rates 5. **In-app UX specifications** — Checklists, tooltips, empty states, progress indicators 6. **Email sequence copy** — Welcome through re-engagement with timing and triggers 7. **Experiment backlog** — Prioritized list of onboarding experiments (impact/confidence/effort) 8. **Measurement framework** — Leading indicators, tracking plan, and success criteria 9. **Risk documentation** — Open questions, assumptions, and next-step recommendations
Stage 1: Signup -> Profile Setup (Target: 90%+) Stage 2: Profile Setup -> First Key Action (Target: 60-70%) Stage 3: First Key Action -> Aha Moment (Target: 50-60%) Stage 4: Aha Moment -> Habit Formation (Target: 30-40%)
Structure onboarding in three layers that unlock sequentially:
1. **Layer 1: Immediate Value (Minutes 0-5)**
2. **Layer 2: Core Setup (Day 1-3)**
3. **Layer 3: Expansion (Week 1-2)**
| Product Type | Common Activation Event | Target Time-to-Value | |-------------|------------------------|---------------------| | B2B SaaS (simple) | Complete first core workflow | < 10 minutes | | B2B SaaS (complex) | Import data + run first report | < 24 hours | | PLG / Self-serve | Invite first team member + collaborate | < 48 hours | | Developer tool | First successful API call or deploy | < 30 minutes | | B2C app | Complete first session/transaction | < 3 minutes |
Prioritize onboarding that
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…