Ux Copy
Draft or critique interface text—buttons, errors, empty states, and onboarding—so flows read clear and human.
Overview
UX Copy is an agent skill most often used in Build (also Ship and Launch) that writes or reviews interface microcopy, errors, empty states, and CTAs using clear concise human-centered patterns.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill ux-copyWhat is this skill?
- Writes or reviews microcopy, error messages, empty states, CTAs, and onboarding text
- Five principles: clear, concise, consistent, useful, human
- Structured error pattern: what happened, why, how to fix
- CTA guidance: verb-led, specific labels (e.g. Create account vs Submit)
- Triggered by phrases like write copy for, what should this button say, review this error message
- Five copy principles: clear, concise, consistent, useful, human
Adoption & trust: 2k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your UI works technically but buttons, errors, and empty states sound vague, robotic, or inconsistent—and users hesitate or mis-tap.
Who is it for?
Solo builders shipping SaaS or mobile UI who need fast, structured copy passes on a single screen or flow.
Skip if: Long-form marketing pages, legal/compliance-only disclaimers without product context, or brand strategy before any UI exists.
When should I use this skill?
Trigger with write copy for, what should this button say?, review this error message, or when naming CTAs, confirmation dialogs, empty states, or onboarding text.
What do I get? / Deliverables
You get reviewed or rewritten copy aligned to context, tone, and constraints, ready to drop into components or design specs.
- Revised or new UI strings
- Copy review notes against principles
- CTA and error-message variants
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is where UI strings ship; this skill is the canonical shelf for microcopy work on screens and components. Frontend surfaces are where CTAs, errors, and empty states live—direct match to day-to-day UI implementation.
Where it fits
Replace generic Submit with verb-led CTAs on a signup form.
Pass all error strings through what happened / why / fix structure before release.
Tighten first-run onboarding hints so new users know the very next action.
Draft placeholder copy on a clickable prototype to test comprehension in user tests.
How it compares
Focused UX microcopy skill—not a full content marketing or SEO writing workflow.
Common Questions / FAQ
Who is ux-copy for?
Indie developers and small teams implementing interfaces in Claude Code, Cursor, or similar agents who need button, error, and empty-state wording on demand.
When should I use ux-copy?
In build when adding screens; in ship during UI review before release; at launch for onboarding and confirmation dialogs—especially when you say write copy for, what should this button say, or review this error message.
Is ux-copy safe to install?
It is a local knowledge-work skill with no implied Drive or shell access; review the Security Audits panel on this Prism page before installing from any marketplace.
SKILL.md
READMESKILL.md - Ux Copy
# /ux-copy > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../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 ```markdown ## 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.