ux-copy

Name: ux-copy
Author: anthropics

2.9kinstalls2.7kforks

How to install ux-copy?

anthropics/knowledge-work-plugins/ux-copy

$npx -y skills add anthropics/knowledge-work-plugins --skill ux-copy

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# /ux-copy
2
3	> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
4
5	Write or review UX copy for any interface context.
6
7	## Usage
8
9	```
10	/ux-copy $ARGUMENTS
11	```
12
13	## What I Need From You
14
15	- Context: What screen, flow, or feature?
16	- User state: What is the user trying to do? How are they feeling?
17	- Tone: Formal, friendly, playful, reassuring?
18	- Constraints: Character limits, platform guidelines?
19
20	## Principles
21
22	1. Clear: Say exactly what you mean. No jargon, no ambiguity.
23	2. Concise: Use the fewest words that convey the full meaning.
24	3. Consistent: Same terms for the same things everywhere.
25	4. Useful: Every word should help the user accomplish their goal.
26	5. Human: Write like a helpful person, not a robot.
27
28	## Copy Patterns
29
30	### CTAs
31	- Start with a verb: "Start free trial", "Save changes", "Download report"
32	- Be specific: "Create account" not "Submit"
33	- Match the outcome to the label
34
35	### Error Messages
36	Structure: What happened + Why + How to fix
37	- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."
38
39	### Empty States
40	Structure: What this is + Why it's empty + How to start
41	- "No projects yet. Create your first project to start collaborating with your team."
42
43	### Confirmation Dialogs
44	- Make the action clear: "Delete 3 files?" not "Are you sure?"
45	- Describe consequences: "This can't be undone"
46	- Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"
47
48	### Tooltips
49	- Concise, helpful, never obvious
50
51	### Loading States
52	- Set expectations, reduce anxiety
53
54	### Onboarding
55	- Progressive disclosure, one concept at a time
56
57	## Voice and Tone
58
59	Adapt tone to context:
60	- Success: Celebratory but not over the top
61	- Error: Empathetic and helpful
62	- Warning: Clear and actionable
63	- Neutral: Informative and concise
64
65	## Output
66
67	```markdown
68	## UX Copy: [Context]
69
70	### Recommended Copy
71	[Element]: [Copy]
72
73	### Alternatives
74	\| Option \| Copy \| Tone \| Best For \|
75	\|--------\|------\|------\|----------\|
76	\| A \| [Copy] \| [Tone] \| [When to use] \|
77	\| B \| [Copy] \| [Tone] \| [When to use] \|
78	\| C \| [Copy] \| [Tone] \| [When to use] \|
79
80	### Rationale
81	[Why this copy works — user context, clarity, action-orientation]
82
83	### Localization Notes
84	[Anything translators should know — idioms to avoid, character expansion, cultural context]
85	```
86
87	## If Connectors Available
88
89	If ~~knowledge base is connected:
90	- Pull your brand voice guidelines and content style guide
91	- Check for existing copy patterns and terminology standards
92
93	If ~~design tool is connected:
94	- View the screen context in Figma to understand the full user flow
95	- Check character limits and layout constraints from the design
96
97	## Tips
98
99	1. Be specific about context — "Error message when payment fails" is better than "error message."
100	2. Share your brand voice — "We're professional but warm" helps me match your tone.
101	3. Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.

People who liked this also viewed

6 picks

Type

ux-copy

2.9kinstalls2.7kforks

View on GitHub

How to install ux-copy?

anthropics/knowledge-work-plugins/ux-copy

$npx -y skills add anthropics/knowledge-work-plugins --skill ux-copy

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /ux-copy
2
3	> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
4
5	Write or review UX copy for any interface context.
6
7	## Usage
8
9	```
10	/ux-copy $ARGUMENTS
11	```
12
13	## What I Need From You
14
15	- Context: What screen, flow, or feature?
16	- User state: What is the user trying to do? How are they feeling?
17	- Tone: Formal, friendly, playful, reassuring?
18	- Constraints: Character limits, platform guidelines?
19
20	## Principles
21
22	1. Clear: Say exactly what you mean. No jargon, no ambiguity.
23	2. Concise: Use the fewest words that convey the full meaning.
24	3. Consistent: Same terms for the same things everywhere.
25	4. Useful: Every word should help the user accomplish their goal.
26	5. Human: Write like a helpful person, not a robot.
27
28	## Copy Patterns
29
30	### CTAs
31	- Start with a verb: "Start free trial", "Save changes", "Download report"
32	- Be specific: "Create account" not "Submit"
33	- Match the outcome to the label
34
35	### Error Messages
36	Structure: What happened + Why + How to fix
37	- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."
38
39	### Empty States
40	Structure: What this is + Why it's empty + How to start
41	- "No projects yet. Create your first project to start collaborating with your team."
42
43	### Confirmation Dialogs
44	- Make the action clear: "Delete 3 files?" not "Are you sure?"
45	- Describe consequences: "This can't be undone"
46	- Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"
47
48	### Tooltips
49	- Concise, helpful, never obvious
50
51	### Loading States
52	- Set expectations, reduce anxiety
53
54	### Onboarding
55	- Progressive disclosure, one concept at a time
56
57	## Voice and Tone
58
59	Adapt tone to context:
60	- Success: Celebratory but not over the top
61	- Error: Empathetic and helpful
62	- Warning: Clear and actionable
63	- Neutral: Informative and concise
64
65	## Output
66
67	```markdown
68	## UX Copy: [Context]
69
70	### Recommended Copy
71	[Element]: [Copy]
72
73	### Alternatives
74	\| Option \| Copy \| Tone \| Best For \|
75	\|--------\|------\|------\|----------\|
76	\| A \| [Copy] \| [Tone] \| [When to use] \|
77	\| B \| [Copy] \| [Tone] \| [When to use] \|
78	\| C \| [Copy] \| [Tone] \| [When to use] \|
79
80	### Rationale
81	[Why this copy works — user context, clarity, action-orientation]
82
83	### Localization Notes
84	[Anything translators should know — idioms to avoid, character expansion, cultural context]
85	```
86
87	## If Connectors Available
88
89	If ~~knowledge base is connected:
90	- Pull your brand voice guidelines and content style guide
91	- Check for existing copy patterns and terminology standards
92
93	If ~~design tool is connected:
94	- View the screen context in Figma to understand the full user flow
95	- Check character limits and layout constraints from the design
96
97	## Tips
98
99	1. Be specific about context — "Error message when payment fails" is better than "error message."
100	2. Share your brand voice — "We're professional but warm" helps me match your tone.
101	3. Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.

People who liked this also viewed

6 picks

Type