Empty State Writer Skill
An empty state is the most-missed onboarding moment: the user arrives and there's nothing there. Done well, it
explains the value, removes confusion, and offers the one action that fills the screen. This skill writes empty
states that teach and activate — not blank voids or generic "No data" labels.
Working from a brief
Given "the empty state for a projects list", write it anyway — infer why the screen is empty, the value of
the feature, and the best first action, labelling assumptions. Cover the distinct empty-state types that apply.
Never hand back a question instead of copy.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- The screen/feature — what normally lives here and its value to the user.
- Why it's empty — first use, the user cleared/completed everything, a search/filter returned nothing, or no access.
- The primary action — what you want them to do (create, connect, invite, import, adjust filters).
- Voice & constraints — tone, and any space/illustration limits.
Output Format
Empty States: [screen]
Write the relevant types (skip those that don't apply):
- First use (no data yet) — headline (the value/outcome), a line on what to do and why it's worth it, and a primary CTA (+ optional secondary like "Learn more" / "Import").
- User-cleared / all done — a positive, reassuring message (inbox zero, all tasks complete) — celebrate, don't alarm.
- No search/filter results — say nothing matched, and offer a way forward (clear filters, broaden, create it).
- Error / no permission — what's wrong and the next step (retry, request access, contact admin) — calm and blame-free.
For each: Headline · Supporting line · Action(s), plus a one-line note on the intended tone/illustration.
Quality Checks
Anti-Patterns
Based On
UX writing & onboarding practice — empty states as activation moments, differentiated by type, with value framing and a single clear action.
Example Trigger Phrases
- "Write an empty state."
- "What should this screen say before there's any data?"
- "Write the no-results state."
- "Write first-run placeholder content."
1---2name: empty-state-writer3description: "Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (first-use, user-cleared, no-results, error/permission), so a blank screen guides instead of confuses."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/empty-state-writer7---89# Empty State Writer Skill1011An empty state is the most-missed onboarding moment: the user arrives and there's nothing there. Done well, it12explains the value, removes confusion, and offers the one action that fills the screen. This skill writes empty13states that teach and activate — not blank voids or generic "No data" labels.1415## Working from a brief1617Given "the empty state for a projects list", **write it anyway** — infer why the screen is empty, the value of18the feature, and the best first action, labelling assumptions. Cover the distinct empty-state *types* that apply.19Never hand back a question instead of copy.2021## Required Inputs2223Ask for these only if they aren't already provided (else infer and label):2425- **The screen/feature** — what normally lives here and its value to the user.26- **Why it's empty** — first use, the user cleared/completed everything, a search/filter returned nothing, or no access.27- **The primary action** — what you want them to do (create, connect, invite, import, adjust filters).28- **Voice & constraints** — tone, and any space/illustration limits.2930## Output Format3132### Empty States: [screen]3334Write the relevant types (skip those that don't apply):3536- **First use (no data yet)** — headline (the value/outcome), a line on what to do and why it's worth it, and a **primary CTA** (+ optional secondary like "Learn more" / "Import").37- **User-cleared / all done** — a positive, reassuring message (inbox zero, all tasks complete) — celebrate, don't alarm.38- **No search/filter results** — say nothing matched, and offer a way forward (clear filters, broaden, create it).39- **Error / no permission** — what's wrong and the next step (retry, request access, contact admin) — calm and blame-free.4041For each: **Headline · Supporting line · Action(s)**, plus a one-line note on the intended tone/illustration.4243## Quality Checks4445- [ ] First-use state explains the value and offers one clear primary action — not just "No items"46- [ ] The distinct types (first-use, cleared, no-results, error/permission) are handled differently and correctly47- [ ] "All done"/cleared states feel positive, not like something is broken48- [ ] No-results states offer a way forward, not a dead end49- [ ] Copy is concise and matches the product voice50- [ ] Each state has a headline, a helpful line, and an action5152## Anti-Patterns5354- [ ] Do not ship a bare "No data" / blank screen — it wastes the best activation moment55- [ ] Do not treat every empty state the same — "nothing yet" is opposite to "all caught up"56- [ ] Do not make a cleared/complete state look like an error57- [ ] Do not offer no action on a first-use state — give the one next step58- [ ] Do not over-explain — a headline, a line, and a button, not a paragraph5960## Based On6162UX writing & onboarding practice — empty states as activation moments, differentiated by type, with value framing and a single clear action.6364## Example Trigger Phrases6566- "Write an empty state."67- "What should this screen say before there's any data?"68- "Write the no-results state."69- "Write first-run placeholder content."