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
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.