agentleFS
nisarthnisarth/claude-skills-store/skills/design/ux-copy/SKILL.md

ux-copy

Skill1 starsChanged 7 months agoMITView on GitHub

Write or review UX copy -- microcopy, error messages, empty states, CTAs, confirmation dialogs, onboarding text. 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. Trigger phrases: "write UX copy", "what should this say", "error message for", "empty state copy", "CTA text", "button label", "confirmation dialog", "onboarding copy", "microcopy for", "review this copy", "tooltip text"

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write clear, helpful, and consistent UX copy: microcopy, error messages, empty states, CTAs, confirmation dialogs, onboarding flows, …

    line 12
  2. Distinctive:

    Use words the user would use, not internal jargon

    line 30
  3. Distinctive:

    Use verb + noun for clarity: "Add member" not "Add"

    line 58
  4. Distinctive:

    Never blame the user

    line 77
  5. Distinctive:

    Never use "Yes" and "No" as button labels.

    line 114
  6. Distinctive:

    Keep tooltips to one sentence.

    line 126
  7. Distinctive:

    Response: Consider whether this is a first-time user or someone who searched/filtered to zero results.

    line 169
  8. Distinctive:

    Response: Write each step with a clear title (what), supportive body text (why + how), and an action-oriented CTA.

    line 173
  9. Distinctive:

    Read it out loud: If it sounds awkward spoken, it reads awkward on screen.

    line 177
  10. Distinctive:

    Be consistent with terminology: If you call it a "workspace" in one place, do not call it a "project" in another.

    line 181
  11. Distinctive:

    Test with real scenarios: Write copy with realistic data (long names, edge cases, error states) not idealized placeholders.

    line 183
  12. Distinctive:

    Maintain a copy library: Document approved patterns for common scenarios (errors, confirmations, empty states) so the team stays consistent.

    line 184

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UX Copy Writing

Write clear, helpful, and consistent UX copy: microcopy, error messages, empty states, CTAs, confirmation dialogs, onboarding flows, tooltips, and notifications.

Workflow

Step 1: Understand the Context

Before writing, clarify:

  1. Where does this copy appear? Button, error, tooltip, modal, empty state, notification, onboarding.
  2. What is the user doing? What task or flow is this part of?
  3. What is the user's emotional state? Neutral, frustrated, confused, excited, anxious?
  4. What should happen next? What action should the copy encourage or explain?
  5. What is the product's voice? Formal, casual, technical, friendly?

Step 2: Apply Copy Principles

Clarity Over Cleverness

  • Say exactly what is happening or what to do
  • Use words the user would use, not internal jargon
  • One idea per sentence

Be Concise

  • Button labels: 1-3 words (verb or verb + noun)
  • Error messages: 1-2 sentences (what happened + how to fix it)
  • Tooltips: 1 sentence
  • Empty states: headline + 1-2 sentences + CTA

Respect the User's Time and Emotion

  • Error states: be helpful, not blaming ("We could not save your changes" not "You made an error")
  • Destructive actions: be clear about consequences without being scary
  • Success states: confirm briefly and move on

Step 3: Write by Copy Type

Buttons and CTAs

| Context | Good | Bad | Why |
|---------|------|-----|-----|
| Primary action | Save changes | Submit | Specific about what happens |
| Destructive | Delete project | Delete | Specific about what is deleted |
| Navigation | View dashboard | Go | Specific about destination |
| Creation | Create workspace | New | Clear verb + object |
| Upgrade | Upgrade to Pro | Learn more | Specific about the action |

Principles:

  • Use verb + noun for clarity: "Add member" not "Add"
  • Match the button label to the page title or dialog heading
  • For destructive actions, name what is being destroyed

Error Messages

### Error Message Format

**Structure**: [What happened] + [Why] + [How to fix it]

**Examples**:
- "Could not save. The file is too large (max 10 MB). Try compressing it or removing some content."
- "This email is already registered. Sign in instead, or use a different email."
- "Connection lost. Your changes are saved locally and will sync when you are back online."

Principles:

  • Lead with what happened, not an error code
  • Tell the user how to fix it
  • Never blame the user
  • Be specific: "Password must be at least 8 characters" not "Invalid password"

Empty States

### Empty State Format

**Headline**: [What this space is for]
**Body**: [Why it is empty and what to do about it]
**CTA**: [Action to populate it]

**Examples**:
- Headline: "No projects yet"
  Body: "Projects help you organize your work. Create your first one to get started."
  CTA: "Create project"

- Headline: "No results found"
  Body: "Try adjusting your filters or search terms."
  CTA: "Clear filters"

Confirmation Dialogs

### Confirmation Dialog Format

**Title**: [Action being confirmed]
**Body**: [Consequence of the action]
**Primary button**: [Verb that matches the action]
**Secondary button**: [Cancel / Go back]

**Example**:
- Title: "Delete this workspace?"
  Body: "This will permanently delete the workspace and all its contents. This cannot be undone."
  Primary: "Delete workspace" (destructive styling)
  Secondary: "Cancel"

Never use "Yes" and "No" as button labels. Use specific verbs.

Tooltips and Help Text

**Format**: [What this thing does or why it matters]

**Examples**:
- "Your display name is visible to other team members"
- "Turning this off will stop email notifications for this project"
- "Last synced 5 minutes ago"

Keep tooltips to one sentence. If you need more, use an info panel or help doc link.

Onboarding Text

**Step title**: [What the user will do]
**Body**: [Why this step matters + brief instruction]
**CTA**: [Action verb]

**Example**:
- Title: "Connect your tools"
  Body: "Link your existing tools to see all your work in one place. You can always add more later."
  CTA: "Connect tools"

Notifications and Toasts

**Format**: [What happened] + [Action if needed]

**Examples**:
- "Changes saved" (no action needed)
- "Project deleted. Undo" (reversible action)
- "Export ready. Download" (action available)
- "Could not send message. Retry" (error with action)

Step 4: Review Checklist

  • Clear: Would a new user understand this without context?
  • Concise: Can any words be removed without losing meaning?
  • Actionable: Does the user know what to do next?
  • Consistent: Does this match the voice and patterns used elsewhere?
  • Accessible: Is the reading level appropriate (aim for grade 6-8)?
  • Inclusive: Free from assumptions about gender, ability, or background?
  • Translatable: Will this work in other languages (avoid idioms, wordplay)?

Examples

Example 1: Error Messages

User: "Write error copy for when a file upload fails." Response: Provide variants based on the reason: file too large ("This file exceeds the 10 MB limit. Try compressing it or choose a smaller file."), wrong format ("This file type is not supported. Upload a PNG, JPG, or PDF."), network error ("Upload interrupted. Check your connection and try again.").

Example 2: Empty States

User: "What should the empty state say for the team members page?" Response: Consider whether this is a first-time user or someone who searched/filtered to zero results. First-time: "No team members yet. Invite your colleagues to start collaborating. [Invite team]." Filtered: "No members match your search. Try a different name or role."

Example 3: Onboarding Flow

User: "Write copy for a 3-step onboarding." Response: Write each step with a clear title (what), supportive body text (why + how), and an action-oriented CTA. Include a skip option if steps are not mandatory. Make the final step feel like a completion: "You are all set. Start exploring your dashboard."

Best Practices

  1. Read it out loud. If it sounds awkward spoken, it reads awkward on screen.
  2. Front-load the important words. "Save changes to continue" scans better than "To continue, please save your changes."
  3. Use sentence case. "Create new project" is friendlier and more readable than "Create New Project."
  4. Avoid double negatives. "Turn off to disable notifications" confuses. "Turn on to receive notifications" is clear.
  5. Be consistent with terminology. If you call it a "workspace" in one place, do not call it a "project" in another.
  6. Write for the worst case. The user reading your error message is already frustrated. Be helpful, not clever.
  7. Test with real scenarios. Write copy with realistic data (long names, edge cases, error states) not idealized placeholders.
  8. Maintain a copy library. Document approved patterns for common scenarios (errors, confirmations, empty states) so the team stays consistent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.