Claude Skill

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 messag

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download plugin87-ux-ui-agent-skills-.claude_skills_ux-writing-278e9d9.zip · 1 KB
Part of plugin87/ux-ui-agent-skills — 18 skills

Install

skills CLI npx skills add https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/ux-writing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install plugin87-ux-ui-agent-skills@llmmart
Git git clone https://github.com/plugin87/ux-ui-agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole plugin87/ux-ui-agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Skill: UX Writing

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

Steps

  1. Read content/voice-tone.md (voice principles, tone spectrum, formulas, microcopy patterns, inclusive language, pre-ship checklist).
  2. Match tone to the user's emotional state (onboarding/success/routine/error/destructive). Higher stress → plainer language.
  3. 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.
  4. Enforce mechanics: sentence case, no ALL CAPS, numerals, no blame on the user, labels (not placeholders), no directional/color-only instructions.
  5. 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).
Files (ux-ui-agent-skills)
  • SKILL.md 2.1 KB
    ---
    name: ux-writing
    description: 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.
    invocation: model
    ---
    
    # Skill: UX Writing
    
    Produce or critique interface copy in the project's voice.
    
    ## Steps
    1. Read `content/voice-tone.md` (voice principles, tone spectrum, formulas, microcopy patterns, inclusive language, pre-ship checklist).
    2. Match tone to the user's emotional state (onboarding/success/routine/error/destructive). Higher stress → plainer language.
    3. 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.
    4. Enforce mechanics: sentence case, no ALL CAPS, numerals, no blame on the user, labels (not placeholders), no directional/color-only instructions.
    5. 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`).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related