Ux writing

Skill plugin87/ux-ui-agent-skills/.claude/skills/ux-writing

Turn Claude into a Senior Design Architect — DTCG design tokens, 42 components, WCAG 2.2 accessibility, any-framework code, 138 design systems, and runnable skills.

Install

npx -y skills add plugin87/ux-ui-agent-skills --skill ux-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing 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.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.1 KB, as published. Nobody here has run it

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).