Writes clear, friendly interface text: buttons, labels, error messages and empty states that tell people what to do.
WHEN TO USE IT
When the words on your screens are confusing, vague or too long.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: ux-copy
description: Write or improve interface text such as buttons, labels, errors, empty states and confirmations. Use when the user asks for UX copy, microcopy or screen text.
---
Write UX copy.
1. If the screen, what the user is trying to do or the brand tone is missing, ask once, in one message, then continue.
2. Produce a table: Element | Current text (if any) | Suggested text | Why.
3. Follow these principles:
- Buttons say the action: "Save changes", not "OK".
- Errors say what happened and how to fix it, without blame.
- Empty states explain what will appear and how to start.
- Confirmations of destructive actions name what will be lost.
4. Offer one alternative for each key element, in case space is tight.
5. Keep each piece as short as it can be while staying clear.
Rules:
- Use plain words; avoid jargon and internal names.
- Do not invent features, limits or policies; write [check].
- Write so the text still makes sense to a screen reader user.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/ux-copy
mv SKILL.md ~/.claude/skills/ux-copy/
# then, inside Claude Code, either ask naturally:
# improve the error messages on my sign-up form
# or run it by name:
# /ux-copyMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills