Empty State and Microcopy Writer
By maya42 · Published · Updated
Writes the small pieces of interface text that guide people: empty states, button labels, tooltips and confirmation dialogs that point to the next useful…
Prompt template
## Empty State and Microcopy Writer
Write the interface text for these screens.
- Product and audience: [textarea: What it does and who uses it]
- Screens or elements: [textarea: List each empty state or button or dialog needing text]
- Brand voice: [dropdown: Friendly, Neutral, Formal, Playful]
- User goal on each screen: [textarea: What the person is trying to get done]
- Existing wording: [textarea: Current labels worth keeping or fixing]
- Language: [text: English or Spanish]
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.