Skills › Knowledge Work Plugins › ux-copy
ux-copy
The facts
Its description
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.
The description the agent reads to decide when to use it.
From its settingsline 3
When it starts
The agent picks this skill when someone is writing or reviewing the words inside an interface — button labels, error messages, empty states, confirmation dialogs, tooltips, loading or onboarding text — or asks for a copy review of something already written. It is a general-purpose UX writing and copy-review skill, not tied to any particular tool or dataset.
Things a person might say (the model's guesses)
- “What should this button say? It currently says 'Submit'.”
- “Write copy for the empty state on our projects dashboard.”
- “Review this error message: 'Payment declined. Try again.'”
A model's summary of when it is used.
A model's reading
What it takes when started
<context or copy to review>
What to type after its name when you start it.
From its settingsline 4
Licence
Apache-2.0, from LICENSE
The terms its author shares it under, which let it be shown here.
From the repositorylicence text
The text
Most marks come from matching words in the file, so treat them as pointers.
1---
2name: ux-copy
3description: 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---
7# /ux-copy
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Write or review UX copy for any interface context.
/ux-copy
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Write or review UX copy for any interface context.
Raw lines 1 to 12Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
19## What I Need From You
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?
What I Need From You
- Context: What screen, flow, or feature?
- User state: What is the user trying to do? How are they feeling?
- Tone: Formal, friendly, playful, reassuring?
- Constraints: Character limits, platform guidelines?
26## Principles
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.
Principles
- Clear: Say exactly what you mean. No jargon, no ambiguity.
- Concise: Use the fewest words that convey the full meaning.
- Consistent: Same terms for the same things everywhere.
- Useful: Every word should help the user accomplish their goal.
- Human: Write like a helpful person, not a robot.
Copy Patterns
Raw lines 34 to 3536### CTAs
37- Start with a verb: "Start free trial", "Save changes", "Download report"
38- Be specific: "Create account" not "Submit"
39- Match the outcome to the label
CTAs
- Start with a verb: "Start free trial", "Save changes", "Download report"
- Be specific: "Create account" not "Submit"
- Match the outcome to the label
41### Error Messages
42Structure: What happened + Why + How to fix
43- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."
Error Messages
Structure: What happened + Why + How to fix
- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."
45### Empty States
46Structure: What this is + Why it's empty + How to start
47- "No projects yet. Create your first project to start collaborating with your team."
Empty States
Structure: What this is + Why it's empty + How to start
- "No projects yet. Create your first project to start collaborating with your team."
49### Confirmation Dialogs
50- 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"
Confirmation Dialogs
- Make the action clear: "Delete 3 files?" not "Are you sure?"
- Describe consequences: "This can't be undone"
- Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"
63## Voice and Tone
65Adapt tone to context:
66- **Success**: Celebratory but not over the top
67- **Error**: Empathetic and helpful
68- **Warning**: Clear and actionable
69- **Neutral**: Informative and concise
Voice and Tone
Adapt tone to context:
- Success: Celebratory but not over the top
- Error: Empathetic and helpful
- Warning: Clear and actionable
- Neutral: Informative and concise
71## Output
73```markdown
74## UX Copy: [Context]
76### Recommended Copy
77**[Element]**: [Copy]
79### Alternatives
80| 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] |
86### Rationale
87[Why this copy works — user context, clarity, action-orientation]
89### Localization Notes
90[Anything translators should know — idioms to avoid, character expansion, cultural context]
91```
Output
## UX Copy: [Context]
### Recommended Copy
**[Element]**: [Copy]
### Alternatives
| Option | Copy | Tone | Best For |
|--------|------|------|----------|
| A | [Copy] | [Tone] | [When to use] |
| B | [Copy] | [Tone] | [When to use] |
| C | [Copy] | [Tone] | [When to use] |
### Rationale
[Why this copy works — user context, clarity, action-orientation]
### Localization Notes
[Anything translators should know — idioms to avoid, character expansion, cultural context]93## If Connectors Available
95If **~~knowledge base** is connected:
96- Pull your brand voice guidelines and content style guide
97- Check for existing copy patterns and terminology standards
99If **~~design tool** is connected:
100- View the screen context in Figma to understand the full user flow
101- Check character limits and layout constraints from the design
If Connectors Available
If ~~knowledge base is connected:
- Pull your brand voice guidelines and content style guide
- Check for existing copy patterns and terminology standards
If ~~design tool is connected:
- View the screen context in Figma to understand the full user flow
- Check character limits and layout constraints from the design
Uses an outside tool ~~knowledge :95
Uses an outside tool ~~design :99
103## Tips
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.
Tips
- Be specific about context — "Error message when payment fails" is better than "error message."
- Share your brand voice — "We're professional but warm" helps me match your tone.
- Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.
From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.