Goal
Write clear, calm interface copy that tells users what happened and what to do next, for every empty, error and confirmation state listed.
Inputs
- Product and users: [product and who uses it]
- Voice: [for example friendly and plain, formal, encouraging]
- Screens and states: [list, for example empty inbox, no search results, payment failed, file too large, offline, delete confirmation]
- Character limits: [heading and body limits if any]
Output format
A table with columns: State, Heading (under 40 characters), Body (under 120 characters), Primary button, Secondary action, Note.
Then provide:
- Two alternative versions for the three most important states.
- A short list of words and phrases to use and to avoid in this product.
Check before answering
- Every error says what went wrong in plain words and how to fix it.
- No blame on the user, no technical codes in the heading, no "Oops" or jokes on serious errors such as payment failures.
- Empty states explain what will appear there and offer the first action.
- Buttons use specific verbs, such as "Upload file" or "Try again", not "OK" or "Submit".
- Destructive confirmations name the item and say whether the action can be undone.
- Copy is understandable to readers whose first language is not English.
- Text stays within the character limits given.






