Generated banner for UX Copy
Generated logo for UX Copy

UX Copy

AnthropicOfficialPublished by Anthropic

  • Skill
  • Content generator
  • Design and creative
  • Apache-2.0
  • No issues found

From the author

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 by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The ux-copy skill provides a structured framework for creating and auditing interface text. It helps designers and developers craft clear, concise, and human-centered copy for various UI elements such as buttons, empty states, error messages, and onboarding flows. By following established UX writing principles, the skill ensures consistency across digital products while adapting tone to the user's emotional state and specific context.

What it does

  • Generates UI copy for buttons, tooltips, and navigation elements.
  • Drafts empathetic and actionable error messages following a standard structure.
  • Creates helpful empty state content to guide users toward their next action.
  • Provides alternative copy options with varying tones for A/B testing or selection.
  • Offers rationale for copy choices based on clarity and user experience goals.
  • Includes localization notes to assist with internationalization and cultural context.

When to use it

  • When designing new UI components that require clear labels or instructional text.
  • When auditing existing error messages to make them more helpful and less frustrating.
  • When writing onboarding sequences to improve user retention and understanding.
  • When you need to ensure consistent terminology across a complex application.
  • When you need to adapt copy to a specific brand voice or tone.

Advantages

  • Promotes consistency by applying standardized patterns for common UI elements.
  • Reduces user friction by focusing on clarity and actionable language.
  • Helps tailor the emotional tone of the interface to the user's current state.
  • Provides structured output that is easy to review and implement in design files.
  • Encourages thoughtful consideration of localization and character constraints.

Usage examples

“write copy for a button that deletes a user account”
The agent provides a clear, action-oriented label like 'Delete account' and suggests a confirmation dialog text that explains the permanent consequences of the action.
“review this error message: 'Error 404: Invalid input'”
The agent identifies the message as too technical and suggests a more helpful alternative like 'We couldn't find that page. Please check the URL or return to the dashboard.'
“write an empty state for a project management app with no tasks”
The agent generates a friendly message: 'No tasks yet. Create your first task to get organized and start tracking your progress.'

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/ux-copy/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip ux-copy.zip -d .agents/skills

Documentation by Anthropic

/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

  1. Clear: Say exactly what you mean. No jargon, no ambiguity.

  2. Concise: Use the fewest words that convey the full meaning.

  3. Consistent: Same terms for the same things everywhere.

  4. Useful: Every word should help the user accomplish their goal.

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

  1. Be specific about context — "Error message when payment fails" is better than "error message."

  2. Share your brand voice — "We're professional but warm" helps me match your tone.

  3. Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.

Files

SKILL.md

/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

  1. Clear: Say exactly what you mean. No jargon, no ambiguity.

  2. Concise: Use the fewest words that convey the full meaning.

  3. Consistent: Same terms for the same things everywhere.

  4. Useful: Every word should help the user accomplish their goal.

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

  1. Be specific about context — "Error message when payment fails" is better than "error message."

  2. Share your brand voice — "We're professional but warm" helps me match your tone.

  3. Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · design/skills/ux-copy · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download ux-copy.zip