mcpbeat

Ux Writing

plugin87/ux-writing

Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.

535 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
482
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill ux-writing

The instruction itself

4 sections, as written by the author

Skill: UX Writing

Produce or critique interface copy in the project's voice.

Steps

  • Read content/voice-tone.md (voice principles, tone spectrum, formulas, microcopy patterns, inclusive language, pre-ship checklist).
  • Match tone to the user's emotional state (onboarding/success/routine/error/destructive). Higher stress → plainer language.
  • Apply the formulas:
  • Buttons: frontload the verb, name the outcome.
  • Confirmation dialogs: the confirm button restates the action and object — "Delete account", not "Delete"/"OK"/"Yes"/"Confirm". The title asks ("Delete account?"), the button answers in matching words. Cancel stays "Cancel". For irreversible/high-stakes actions, require a type-to-confirm step (WCAG 3.3.4/3.3.6).
  • Errors: what happened → why → how to fix (no dead ends, no codes/stack traces).
  • Empty states: value → first action.
  • Enforce mechanics: sentence case, no ALL CAPS, numerals, no blame on the user, labels (not placeholders), no directional/color-only instructions.
  • Run the 10-item pre-ship copy checklist.

Output

Final copy (or a redline review) that reads naturally aloud and passes the checklist. Keep within any character limits for tight UI.

Verification (mandatory before declaring done)

Run every line through the 10-item pre-ship checklist in content/voice-tone.md — do not skip it:

  • Reads naturally aloud; frontloaded verb on actions; no jargon/blame/dead-ends.
  • Errors follow what→why→how; empty states give value→action; no bare "No data"/"Error".
  • Mechanics: sentence case, numerals, labels (not placeholders), no color/direction-only cues, inclusive language.
  • Within character limits; translatable (no concatenation — see accessibility/i18n-rtl.md).

How to use it

Copy the folder

Take plugin87/ux-writing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.