---
name: empty-state-and-microcopy-writer
description: "Writes the small pieces of interface text that guide people: empty states, button labels, tooltips and confirmation dialogs that point to the next useful action. Use when an interface needs its empty states, button labels, tooltips or confirmation dialogs written or tightened to guide users. Do not use for long-form marketing copy or translating an entire interface. Related topics: design, writing."
---

# Empty State and Microcopy Writer

Writes the small pieces of interface text that guide people: empty states, button labels, tooltips and confirmation dialogs that point to the next useful action.

## When to use

Use this skill when an interface needs its empty states, button labels, tooltips or confirmation dialogs written or tightened to guide users. Do not use it for long-form marketing copy or translating an entire interface.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the user's goal for each screen or element before writing any text.
3. Write empty states with a headline, a one-line reason and one action, and button labels as a verb plus an object.
4. Write tooltips and confirmations that name the affected thing, state the consequence and repeat the action in the button.
5. Check terms, capitalisation and punctuation for consistency across every screen.
6. Offer two options for key screens and flag text that needs legal or safety review.

## Inputs

- **Product and audience** (longer free text)
- **Screens or elements** (longer free text)
- **Brand voice** (choose one: Friendly, Neutral, Formal, Playful)
- **User goal on each screen** (longer free text)
- **Existing wording** (longer free text)
- **Language** (free text, e.g. "English or Spanish")

## Output

A table by screen and element giving the final text, with two options for key screens and a short list of items needing review.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Empty State and Microcopy Writer

Write the interface text for these screens.

- Product and audience: {{Product and audience}}
- Screens or elements: {{Screens or elements}}
- Brand voice: {{Brand voice}}
- User goal on each screen: {{User goal on each screen}}
- Existing wording: {{Existing wording}}
- Language: {{Language}}

For every element, start from the user's goal and write the shortest text that moves them toward it. Empty states get three parts: a headline saying what will appear here, one line on why it is empty or why it is worth filling, and a single clear action button. Button labels use a verb plus the object ("Save draft", "Invite teammate"), never "Submit" or "OK" where something more specific exists. Tooltips explain what and why in one sentence, not how to use an obvious control. Confirmations for destructive actions name the thing being affected, state the consequence, and use a button label that repeats the action ("Delete project") with a safe cancel. Keep terms consistent across screens and keep punctuation and capitalisation uniform. Give two options for the important screens, flag any text that needs legal or safety review, and return everything in a table by screen and element.

## Pitfalls

- Using generic labels such as OK or Submit, which hide what will actually happen.
- Filling an empty state with a paragraph, when one line and one action get people moving.
- Calling the same thing by different names on different screens, which makes users doubt they are the same.