$ ~/registry/skill/anthropics-design-skills-ux-copy

SKILL

ux-copy

Name: ux-copy
Author: anthropics

Write and refine UX copy for buttons, errors, empty states, and onboarding.

Stars

★ 29,577

Source

GitHub

Updated

2026-10-14

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 29.6k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "ux-copy" skill from askskill:
1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/design/skills/ux-copy/SKILL.md
2. Save it as ~/.claude/skills/ux-copy/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Improve an error message

Prompt

Please review this login failure message and provide 3 clearer, friendlier alternatives: "Something went wrong. Please try again." Make the cause clearer, reduce frustration, and keep it concise.

Expected

Returns several clearer error message options with notes on tone and best use cases.

Name a CTA button

Prompt

I’m designing a subscription checkout page. The main button starts a free trial. Give me 10 CTA button options that are concise and action-oriented, grouped into direct, benefit-led, and low-pressure styles.

Expected

Provides multiple CTA options grouped by style for easier brand and conversion alignment.

Write empty state copy

Prompt

Write empty state copy for a new task management app. The user has not created any tasks yet. Please provide a headline, supporting text, and one CTA button label in an encouraging but unobtrusive tone.

Expected

Generates a complete empty state set, including headline, body copy, and CTA suggestion.

// docs

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

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.