Ux Copy

1---2name: ux-copy3description: Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.4argument-hint: "<context or copy to review>"5---6 7# /ux-copy8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Write or review UX copy for any interface context.12 13## Usage14 15```16/ux-copy $ARGUMENTS17```18 19## What I Need From You20 21- **Context**: What screen, flow, or feature?22- **User state**: What is the user trying to do? How are they feeling?23- **Tone**: Formal, friendly, playful, reassuring?24- **Constraints**: Character limits, platform guidelines?25 26## Principles27 281. **Clear**: Say exactly what you mean. No jargon, no ambiguity.292. **Concise**: Use the fewest words that convey the full meaning.303. **Consistent**: Same terms for the same things everywhere.314. **Useful**: Every word should help the user accomplish their goal.325. **Human**: Write like a helpful person, not a robot.33 34## Copy Patterns35 36### CTAs37- Start with a verb: "Start free trial", "Save changes", "Download report"38- Be specific: "Create account" not "Submit"39- Match the outcome to the label40 41### Error Messages42Structure: What happened + Why + How to fix43- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."44 45### Empty States46Structure: What this is + Why it's empty + How to start47- "No projects yet. Create your first project to start collaborating with your team."48 49### Confirmation Dialogs50- Make the action clear: "Delete 3 files?" not "Are you sure?"51- Describe consequences: "This can't be undone"52- Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"53 54### Tooltips55- Concise, helpful, never obvious56 57### Loading States58- Set expectations, reduce anxiety59 60### Onboarding61- Progressive disclosure, one concept at a time62 63## Voice and Tone64 65Adapt tone to context:66- **Success**: Celebratory but not over the top67- **Error**: Empathetic and helpful68- **Warning**: Clear and actionable69- **Neutral**: Informative and concise70 71## Output72 73```markdown74## UX Copy: [Context]75 76### Recommended Copy77**[Element]**: [Copy]78 79### Alternatives80| Option | Copy | Tone | Best For |81|--------|------|------|----------|82| A | [Copy] | [Tone] | [When to use] |83| B | [Copy] | [Tone] | [When to use] |84| C | [Copy] | [Tone] | [When to use] |85 86### Rationale87[Why this copy works — user context, clarity, action-orientation]88 89### Localization Notes90[Anything translators should know — idioms to avoid, character expansion, cultural context]91```92 93## If Connectors Available94 95If **~~knowledge base** is connected:96- Pull your brand voice guidelines and content style guide97- Check for existing copy patterns and terminology standards98 99If **~~design tool** is connected:100- View the screen context in Figma to understand the full user flow101- Check character limits and layout constraints from the design102 103## Tips104 1051. **Be specific about context** — "Error message when payment fails" is better than "error message."1062. **Share your brand voice** — "We're professional but warm" helps me match your tone.1073. **Consider the user's emotional state** — Error messages need empathy. Success messages can celebrate.