How do I install the UX Copy skill?

Run npx skillmds@latest add nota-america/ux-copy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is UX Copy safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with UX Copy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is UX Copy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published UX Copy?

nota-america (@nota-america) published this skill. Their other Agent Skills are listed on their SkillMD profile.

UX Copy by nota-america — Agent Skill

Name: UX Copy
Author: nota-america

UX Copy

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.

nota-america Updated Sep 17, 2026

File contents

/ux-copy

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md ({{ref:connectors}}).

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.

---name: ux-copydescription: 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.---# /ux-copy> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (`{{ref:connectors}}`).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?## Principles1. **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 MessagesStructure: What happened + Why + How to fix- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."### Empty StatesStructure: 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 ToneAdapt 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 AvailableIf **~~knowledge base** is connected:- Pull your brand voice guidelines and content style guide- Check for existing copy patterns and terminology standardsIf **~~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## Tips1. **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.

Frequently asked questions