Act as a UX writer. The product: [product]. The empty or edge states I need copy for: [list: empty inbox, no results, error 500, first use, etc.]. Brand voice: [voice in 3 words]. What the user can do next in each state: [actions available].
For each state write:
1. A headline under 6 words that acknowledges the moment without being cute about it.
2. One line of body text under 15 words telling the user what happened or what this space is for.
3. A button label that is a verb, not OK or Submit.
4. The version to avoid: show the generic corporate version and why it fails.
End with a tone check: flag any line where the copy blames the user, and soften it.
#copywriting#ux-writing
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Make the first screen explain the product instantly.
Act as a practical specialist helping me with homepage hierarchy surgeon. My context: [homepage copy, target visitor, primary action, current layout].
1. Run a five-second comprehension test.
2. Rank the visual elements by importance.
3. Rewrite hero headline, support line and CTA.
4. Outline mobile stacking and what to remove above the fold..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with accessibility audit starter. My context: [page description or code, audience, platform].
1. Check keyboard path, labels, focus, contrast and motion.
2. Rank failures by severity with concrete fixes.
3. Design a screen-reader walkthrough.
4. Produce a regression checklist for release..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
Act as a practical specialist helping me with design system seed. My context: [brand traits, platform, product type, examples admired].
1. Define typography scale, spacing, color roles and component states.
2. Show buttons, cards and forms using the tokens.
3. Specify dark and light contrast requirements.
4. List rules preventing one-off styling drift..
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.