From user-docs-writer
Write onboarding content — welcome flow, getting-started guide, or first-run experience. Optimised for time-to-first-value. Use when creating new user onboarding or improving activation rates.
npx claudepluginhub hpsgd/turtlestack --plugin user-docs-writerThis skill is limited to using the following tools:
Write onboarding content for $ARGUMENTS using the mandatory process and structure below.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
Write onboarding content for $ARGUMENTS using the mandatory process and structure below.
Core principle: The fastest path from signup to genuine value. Every sentence either moves the user closer to their "aha moment" or gets cut.
Before writing, map the journey from signup to value:
### Value path
| Element | Definition |
|---|---|
| **Target user** | [Who, what they know, what they want] |
| **Aha moment** | [Specific experience that delivers first value] |
| **Minimum steps** | [Count] steps to reach aha moment |
| **Time target** | [Minutes] from signup to aha moment |
| **Primary drop-off risk** | [Where and why users abandon] |
Output: Completed value path table.
The first screen or section after signup. Must answer three questions instantly:
## Welcome to [Product]
[One sentence: what the product does for THEM — not what it is, but what it enables.]
**In the next [N] minutes, you'll [specific outcome].**
Here's what we'll do:
1. [First action — framed as benefit, not task]
2. [Second action]
3. [Third action — this is the aha moment]
Rules for the welcome:
Output: Welcome section with time commitment and step preview.
Each step in the onboarding flow follows this format:
## Step N: [Action verb] [what they'll accomplish]
[One sentence: why this step matters to THEM.]
### What to do
1. [Specific action with exact UI location: "Click **New Project** in the top-right corner"]
2. [Next action with example input: "Enter a project name, e.g., 'My first dashboard'"]
3. [Final action for this step]
### You should see
[Describe or show what the user should see after completing the step.
Include a description of the expected UI state.]
### If something's not right
- **[Problem]:** [One-line fix — e.g., "If the button is greyed out, check that you've verified your email"]
Rules for each step:
Output: All onboarding steps with actions, expected results, and troubleshooting.
When the user reaches the value moment, confirm it explicitly:
## You're set up!
[One sentence celebrating what they just accomplished — specific to what they built/created/configured.]
### What you just did
- [Concrete outcome 1 — e.g., "Created your first project with live data"]
- [Concrete outcome 2 — e.g., "Set up your first automated alert"]
### What to explore next
| If you want to... | Go here |
|---|---|
| [Common next goal] | [Link with brief description] |
| [Second common goal] | [Link with brief description] |
| [Power-user goal] | [Link with brief description] |
Rules for the aha moment:
Output: Completion confirmation with specific outcomes and next steps.
| Check | Requirement |
|---|---|
| Time test | Can a new user complete the full onboarding in the stated time? |
| Aha moment reached | Does the flow end with the user seeing real value, not just a configured state? |
| No jargon | Would a first-time user understand every term without a glossary? |
| One action per step | Does each step do exactly one thing? |
| Expected results present | Does every step show what success looks like? |
| Escape hatches | Does every step have a "if this didn't work" fallback? |
| Progressive disclosure | Is information revealed only when needed, not all at once? |
| Example inputs provided | Does every input field have a suggested value? |
/user-docs-writer:write-user-guide for comprehensive feature docs and /user-docs-writer:write-kb-article for specific questions.# Getting Started with [Product] — [User Type]
**Time to complete:** [N] minutes
**What you'll accomplish:** [Specific outcome]
## Welcome
[Welcome section from Step 2]
## Step 1 of [N]: [First action]
[Step content from Step 3]
## Step 2 of [N]: [Second action]
[Step content]
## Step 3 of [N]: [Aha moment action]
[Step content]
## You're set up!
[Confirmation from Step 4]
---
Last verified: [date]
Product version: [version]