Onboarding + Activation Designer
Do not use when
- •The request is unrelated to this domain or requires a different specialized skill.
- •The user asks only for high-level discussion without applying this workflow.
- •Another skill has a tighter, more specific trigger for the same request.
Example user requests
- •"Apply onboarding activation designer to improve this feature."
- •"Use onboarding activation designer and give me the concrete deliverables."
- •"Can you run a full onboarding activation designer pass on this repo?"
- •"I need step-by-step execution using onboarding activation designer."
Goal
Turn UI into a product via onboarding and activation mechanics.
When to use
- •First-time UX unclear.
- •Empty dashboards.
Minimal inputs (ask only if missing)
- •Activation moment definition.
Procedure (MUST)
- •Define activation goal.
- •Guided empty states + quick start.
- •Progressive disclosure.
- •Confirmation + next-step prompts.
- •Instrument key steps (no PII).
Outputs (MUST produce)
- •
docs/onboarding_plan.md. - •Onboarding + empty-state components.