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”

Onboarding

Progressive disclosure, one concept at a time

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

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]

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

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.

About this skill

Trigger

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 verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/knowledge-work-plugins, branch main, last pushed 23 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 27 distinct layouts observed: bio-research/skills/*/SKILL.md, cowork-plugin-management/skills/*/SKILL.md, customer-support/skills/*/SKILL.md, data/skills/*/SKILL.md, design/skills/*/SKILL.md, engineering/skills/*/SKILL.md, enterprise-search/skills/*/SKILL.md, finance/skills/*/SKILL.md, human-resources/skills/*/SKILL.md, legal/skills/*/SKILL.md, marketing/skills/*/SKILL.md, operations/skills/*/SKILL.md, partner-built/apollo/skills/*/SKILL.md, partner-built/brand-voice/skills/*/SKILL.md, partner-built/common-room/skills/*/SKILL.md, partner-built/slack/skills/*/SKILL.md, partner-built/zoom-plugin/skills/*/SKILL.md, partner-built/zoom-plugin/skills/contact-center/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/web/*/SKILL.md, partner-built/zoom-plugin/skills/video-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/virtual-agent/*/SKILL.md, partner-built/zoom-plugin/skills/zoom-mcp/*/SKILL.md, pdf-viewer/skills/*/SKILL.md, product-management/skills/*/SKILL.md, productivity/skills/*/SKILL.md, sales/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “/ux-copy”, a leading h1 that duplicated the skill title.

Spec compliance

53 editorial notes across 41 of 200 skills. They are printed in the margin of each skill rather than as errors here.

and 31 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Anthropic, declaring 120 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/knowledge-work-plugins.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (opens in a new tab).

Write or review UX copy for any interface context.

Usage

/ux-copy $ARGUMENTS

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?

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

CTAs

Start with a verb: “Start free trial”, “Save changes”, “Download report”
Be specific: “Create account” not “Submit”
Match the outcome to the label

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.”

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.”

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”

Tooltips

Concise, helpful, never obvious

Loading States

Set expectations, reduce anxiety

Onboarding

Progressive disclosure, one concept at a time

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

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]

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

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.