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.
SkillScore91Maintained
Automatic
◆Design & UX Review pack
Last verified 10/10/2026
What it changes
Passed 20 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill91%
Checks it passed that the model alone missed
Each button label uses sentence case
All navigation headers use sentence case
The primary action button uses sentence case
and 1 more in the full report
4 fixed16 passed either way2 still failing0 broke1 errored
Pass-rate lift
+18 pp
Tokens
+90%
Agent turns
0%
Response time
+58%
Model gemini-3.6-flashMeasured 10/10/2026v220 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
When checking an environment where the kit tokens folder at CLAUDE_SKILL_DIR/../../../tokens is missing, what status indicator (KIT_MISSING or KIT_OK) and CLI command guidance should be reported?
What was checked, without and with the skill
Checked
Without skill
With skill
The response includes the status indicator KIT_MISSING
Passed
Passed
The response instructs the user to run npx ux-ui-agent-skills init
Missed
Passed
case-10 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md31 linessingle file
Skill: UX Writing
Step 0 — is the kit here? This skill reads files from the kit. Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING
On KIT_MISSING only the skill folders were installed, which is what
npx skills add does. Say so plainly, point the user at
npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the
contents of a file you could not open.
Produce or critique interface copy in the project's voice.
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 ${CLAUDE_SKILL_DIR}/../../../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".