Write UX microcopy for buttons, errors, and empty states
Clear, on-brand interface text for buttons, form errors, empty states, and confirmations.
The prompt
Write microcopy for a screen or flow in my product or website.
Screen or flow: [e.g. "checkout", "sign-up form", "dashboard with no data yet"]
What the user is trying to do: [GOAL]
Elements that need copy: [buttons, field labels, helper text, error messages, empty states, tooltips, confirmations, success messages]
Technical constraints: [character limits, localization needs]
Brand voice: [e.g. "friendly but not cute"]
Current copy (if rewriting): [PASTE]
Rules:
- Buttons: verb + object ("Save changes", not "Submit" or "OK").
- Errors: say what happened, why if useful, and how to fix it. No blame, no codes alone, no jokes on serious errors (payment, data loss).
- Empty states: explain what will appear here and give one action to get started.
- Confirmations for destructive actions: name the consequence ("Delete 3 files? This can't be undone.").
- Use the same term for the same thing everywhere.
- Plain language, sentence case, front-load the key word.
Return a table: | Element | Copy | Character count | Note |
Then flag any spot where the flow itself is confusing and copy alone won't fix it.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- e.g. "checkout", "sign-up form", "dashboard with no data yet"
- GOAL
- character limits, localization needs
- e.g. "friendly but not cute"
- PASTE
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Write design principles my team will actually useDrafts a short set of specific, decision-ready design principles for your product, with examples of how each settles real trade-offs.
- Set up readable, responsive typography for my websiteProduction-ready CSS for body text, a type scale, font loading, and responsive sizing based on proven typography rules.
- Design empty states that help people get startedGives you content and layout guidance for every empty state in a feature: first use, no results, cleared, and no permission.
- Run a UX teardown of a competitor's product flowBreaks down how competitors handle a specific user flow step by step, comparing patterns, friction, and ideas worth borrowing or avoiding.