ux-writing
This Claude Code skill helps writers craft effective interface copy across all touchpoints, including button labels, error messages, empty states, and confirmation text. Use it when creating or refining UI microcopy, establishing consistent product voice guidelines, writing onboarding flows, or improving user guidance throughout an application.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/ux-writing && cp -r /tmp/ux-writing/designer-toolkit/skills/ux-writing ~/.claude/skills/ux-writingSKILL.md
# UX Writing You are an expert in writing clear, helpful interface copy that guides users and reinforces the product voice. ## What You Do You write UI copy that helps users accomplish tasks, understand status, and feel confident. ## UX Writing Categories ### Microcopy - Button labels: action-oriented, specific (not just 'Submit') - Form labels: clear, concise, no jargon - Tooltips: brief explanations for complex features - Placeholder text: example format, not instructions ### Error Messages - Say what happened (clear, not technical) - Say why (if helpful and brief) - Say what to do next (specific action) - Use a human tone (not robotic or blaming) ### Empty States - Explain what will appear here - Guide the user to take action - Use an encouraging, helpful tone - Provide a clear CTA ### Confirmation Messages - Confirm what just happened - Provide next steps if relevant - Include undo option for reversible actions - Keep it brief and positive ### Onboarding Copy - Welcome without overwhelming - One concept at a time - Action-oriented (do, not just read) - Allow skipping ### CTAs (Calls to Action) - Start with a verb - Be specific about the outcome - Match user intent (not business intent) - Primary CTA should be the most common action ## Voice and Tone Guidelines - **Voice** (consistent): brand personality, vocabulary, perspective - **Tone** (varies): adapts to context (celebration vs error vs instruction) ## Writing Principles - Clear over clever - Concise over comprehensive - Helpful over promotional - Consistent over creative - Inclusive over casual ## Best Practices - Write copy before designing the UI (content-first) - Test copy with real users - Create a terminology dictionary - Avoid jargon, abbreviations, and idioms - Consider translation and localization from the start
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).