Ux writing
Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/ux-writing
Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and cited by AI systems.
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill ux-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Write effective UI copy including microcopy, error messages, empty states, and CTAs.
SKILL.md
1.9 KB, as published. Nobody here has run it
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