
Ux Writing
This one coaches Claude to write interface copy that actually helps users instead of sounding like a robot wrote it. It covers the essentials: microcopy for buttons and forms, error messages that explain what happened and what to do next, empty states that guide action, and CTAs that start with verbs. The principles are solid, clear over clever, concise over comprehensive, and it pushes you to think about content before designing the UI. Useful if you're building products and tired of placeholder text making it to production or error messages that just say "Error: something went wrong."
- skills.sh installs
- 2.4K
- GitHub stars
- 3.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add owl-listener/designer-skills --skill ux-writing --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Details
- Repository
- github.com/owl-listener/designer-skills
- Categories
- Documentation, Debugging, Design & UI/UX
- First seen
- Jun 3, 2026
More from owl-listener/designer-skills
All 68- Journey Map2.4K
- Component Spec2.4K
- Design Principles2.4K
- Theming System2.4K
- Competitive Analysis2.3K
- Feedback Patterns2.3K
- Design Brief2.3K
- Prototype Strategy2.3K
- User Persona2.3K
- Jobs To Be Done2.3K
- Gesture Patterns2.3K
- Handoff Spec2.3K
- Experience Map2.3K
- Naming Convention2.3K
- Empathy Map2.3K
- Documentation Template2.3K
- Pattern Library2.3K
- Affinity Diagram2.3K
- Interview Script2.3K
- Card Sort Analysis2.3K
- Design Rationale2.3K
- Accessibility Test Plan2.3K
- A B Test Design2.3K
- Metrics Definition2.3K