Onboarding

/sunboard.onboarding is where you start. You describe what you want ("help me set up onboarding"); it runs a short conversation, agrees on a plan with you, then drives the whole build itself — the survey, one experience per cohort, the segments that route them, the selector/event wiring, the preview, and the deploy. You answer questions and approve the plan; you don't run the other skills by hand.

When to use it

• Setting up onboarding from scratch.
• Making a structural change — adding a cohort, introducing a survey, or reshaping the whole flow.
• Any time you'd otherwise have to figure out which skills to run in what order.

What happens

1. Studies your product and hosted state — routes, how you load the user (what's already on the user object), and what's already deployed.
2. Finds the aha moment — the first measurable "this worked" event the whole flow should drive toward.
3. Decides one path or many — does the route to value differ by who the user is? If not, one catch-all experience. If so, it names the cohorts (e.g. enterprise vs. self-serve) and what's different about each.
4. Decides how it knows the cohort — a property your app already passes (plan, role) → segment on it; something you don't know at signup → a survey question collects it.
5. Designs the path per cohort — a short checklist toward the aha, plus a tour only where a screen genuinely needs guiding.
6. Shows you the plan and waits for approval — the activation event, any survey, each experience, the segments, the wiring needed. Nothing is written or deployed until you say yes.
7. Carries it out — runs Survey, Spec (once per cohort), Tour, Implement, Segment, Preview, and Deploy for you, in order.
8. Offers to style it — Survey UI and Checklist UI to match your design system.

Related