Ux writing
Write or improve interface copy — button labels, error messages, empty states, confirmations, tooltips, onboarding text. Use when the user asks for microcopy, UX writing, copy review, or "make this clearer." Distinct from marketing copywriting.From its SKILL.md
npx -y skills add rafa-js/product-designer --skill ux-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.9 KB, as published. Nobody here has run it
UX Writing
Write copy that helps users complete tasks. Brevity, clarity, and the user's words.
Inputs to confirm
- Surface: which element (button, error, empty state, modal, etc.).
- Context: what just happened, what the user is trying to do, what happens next.
- Voice: does the product have a published voice & tone? Mirror it if so.
- Constraints: character limits, localization (English copy is often the shortest), reading level.
If the team's voice isn't documented, infer it from 2–3 existing in-product strings and confirm.
Core principles
- Clear before clever. If a user has to re-read, you've failed.
- Plain language. Grade 8 reading level; lower for stress flows (medical, financial, errors).
- Active voice, second person. "Add your card" beats "A card should be added by you."
- Verbs in buttons. "Save changes," "Send invite," "Delete account" — never "OK" or "Submit" alone.
- Concrete > abstract. "Choose a date" beats "Select an option."
- Numbers, not words. "5 results" beats "Several results."
- Sentence case for UI (most products); reserve Title Case for brand moments.
- Don't shout. No ALL CAPS for body copy.
Full guide: references/08-ui-and-design-systems/content-and-ux-writing.md.
Method by surface
Buttons
- 1–3 words. Verb-led.
- Match the verb to what will happen, exactly. ("Send" sends; "Save" saves; "Continue" advances.)
- Don't pair "OK" with anything destructive. Use the verb.
- If you can't fit the verb, the button is wrong, not the copy.
Error messages
Structure: what went wrong + why + what to do.
- Bad: "Invalid input."
- Better: "Email must include @ — try
[email protected]."
Place the message next to the field. Use plain language; never expose error codes alone.
Empty states
Structure: what would appear here + how to make something appear.
- Bad: "No items found."
- Better: "No projects yet — create your first one to get started." + a button.
If the empty state is permanent (no permission, no data possible), explain why.
Confirmation dialogs
Lead with the consequence, not the verb.
- Bad: "Are you sure?"
- Better: "Delete this project? All linked tasks will be removed."
Buttons in confirm dialogs name the action, not "OK/Cancel": Delete project / Keep.
Tooltips
- ≤ 1 sentence.
- Add info, don't restate the label.
- Never put critical info here — users skip tooltips.
Onboarding
- Stop after the user's first successful primary action; don't milestone-shame.
- Replace tours with in-line guidance that appears where it matters.
- Skippable, always.
Microcopy for AI features
- Set expectations up front: what the AI can/can't do.
- Mark drafts as drafts; confirm before consequential actions.
- "Suggested" ≠ "applied" — distinguish in UI.
See references/11-designing-beyond-screens/ai-and-ux.md.
Output
When rewriting, return:
| # | Original | Rewritten | Why |
## Notes on voice / system consistency
- [issues you noticed beyond the specific strings]
When writing from scratch, return the strings with brief inline notes on choices, and flag any string you weren't given enough context for.
Things to refuse
- Writing copy without knowing what action follows. ("Continue" to where? "Save" what?)
- Filling in marketing voice where the user is reading an error.
- Writing length to fill a design's whitespace — push back on the design instead.
Hand-off
- Tone or systemic content gaps → recommend establishing a voice/tone doc; offer to draft.
- Localization concerns → flag explicitly so a localization specialist can review.