Ux Copy
- 3k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
ux-copy is an agent skill that writes or reviews UX microcopy for CTAs, errors, empty states, confirmations, and onboarding using clear concise human patterns.
About
ux-copy is a slash-command skill for writing or reviewing interface copy across CTAs, error messages, empty states, confirmation dialogs, tooltips, loading states, and onboarding text. It asks for screen context, user goal, emotional state, tone, and character limits before producing recommendations. Principles enforce clarity without jargon, concise wording, consistent terminology, usefulness toward the user goal, and human tone rather than robotic phrasing. Pattern tables define verb-first specific CTAs, error structure of what happened plus why plus fix steps, empty states explaining what the area is and how to start, and confirmation dialogs that name the action and consequences with action-labeled buttons instead of OK or Cancel. Output format returns recommended copy, alternatives table with tone notes, rationale tied to user context, and localization cautions about idioms or expansion. Optional connectors can pull brand voice from a knowledge base or layout constraints from a design tool when available. Triggers include write copy for, button label questions, error message review, and onboarding wording tasks.
- Covers CTAs, errors, empty states, confirmations, tooltips, loading, and onboarding patterns.
- Error template: what happened, why, and how to fix in plain language.
- Confirmation dialogs use action labels like Delete files instead of OK or Cancel.
- Output includes recommended copy, alternatives table, rationale, and localization notes.
- Adapts voice for success, error, warning, and neutral interface contexts.
Ux Copy by the numbers
- 3,018 all-time installs (skills.sh)
- +153 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #111 of 1,896 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
ux-copy capabilities & compatibility
- Capabilities
- cta labeling with verb first specific outcomes · structured error, empty state, and confirmation · tone adaptation for success, error, warning, and · alternatives table with tone and use case guidan · localization notes for translators on idioms and
- Works with
- figma · notion
- Use cases
- ui design · copywriting · frontend
What ux-copy says it does
Structure: What happened + Why + How to fix
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill ux-copyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
What should this button, error, or empty state say so users understand the action and next step without jargon?
Write or review UX microcopy for CTAs, errors, empty states, confirmations, tooltips, loading text, and onboarding flows.
Who is it for?
Product and design teams drafting or reviewing interface text when context, tone, and constraints are known.
Skip if: Skip for long-form marketing pages, legal policy drafting, or deep brand strategy without a specific UI element.
When should I use this skill?
User asks to write copy for a button, error message, empty state, confirmation dialog, tooltip, or onboarding step.
What you get
Recommended interface copy with alternatives, rationale, and localization notes formatted for design or engineering handoff.
- recommended UX copy block
- alternatives table
- rationale and localization notes
Files
/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 $ARGUMENTSWhat 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.
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kFAQ
How should error messages be structured?
State what happened, why it happened, and how to fix it, for example a declined card with bank contact guidance.
What makes a good CTA label?
Start with a verb, be specific about the outcome, and match the label to what the user receives after clicking.
How should confirmation dialogs label buttons?
Use action names like Delete files and Keep files instead of generic OK or Cancel.
Is Ux Copy safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.