About ux-writing
ux-writing is a skill for creating clear interface copy that helps users complete tasks and understand product status. It covers microcopy, errors, empty states, confirmations, onboarding, and calls to action, with guidance on voice, tone, and localization.
Key features
- 01Action-oriented button labels
- 02Clear form labels and tooltips
- 03Helpful error and empty-state messages
- 04Brief confirmations and onboarding copy
- 05Voice, tone, and localization guidance
Use cases
- 01Writing labels for forms and buttons
- 02Explaining errors and next steps
- 03Guiding users through empty states
- 04Preparing onboarding and confirmation text
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ infrasity-labs/ dev-gtm-claude-skills --skill ux-writingAfter installing, type/ux-writingin Claude Code to confirm it loaded.
Details
From the project READMEUX 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
Comments
Markdown supported