
Ux Writing
- 980 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
ux-writing is a designer agent skill that generates clear, on-brand UI microcopy, error messages, empty states, CTAs, and onboarding text for developers building interfaces that guide users without confusion.
About
ux-writing is an owl-listener/designer-skills module for crafting effective interface copy across microcopy, error messages, empty states, CTAs, and onboarding flows. The skill instructs agents to write action-oriented button labels instead of generic Submit, concise form labels without jargon, brief tooltips, and placeholder text showing example formats rather than instructions. Error messages must state what happened, optionally why, and how to recover in plain language. Developers reach for ux-writing when shipping SaaS or mobile UI where copy quality directly affects task completion, status comprehension, and product voice consistency across screens.
- Covers six UX writing categories: Microcopy, Error Messages, Empty States, Confirmation Messages, Onboarding Copy, and C
- Produces action-oriented button labels, specific form labels, helpful tooltips and example-rich placeholders
- Writes human-toned error messages that explain what happened, why, and exactly what to do next
- Creates encouraging empty states with clear CTAs and positive confirmation messages that offer undo options
- Delivers progressive onboarding flows that introduce one concept at a time while matching product voice and tone
Ux Writing by the numbers
- 980 all-time installs (skills.sh)
- +44 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #401 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill ux-writingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 980 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you write clear UI microcopy and error messages?
Generate clear, on-brand microcopy, error messages, empty states, CTAs and onboarding text that guides users without confusion.
Who is it for?
Frontend developers and designers shipping SaaS or mobile interfaces who need consistent, task-oriented UI copy across forms, errors, and empty states.
Skip if: Developers drafting long-form marketing pages, API reference documentation, or legal compliance text unrelated to in-app interface elements.
When should I use this skill?
The user mentions UX writing, microcopy, error messages, empty states, button labels, CTAs, or onboarding screen text.
What you get
Button labels, form labels, tooltips, error message copy, empty state text, CTA strings, and onboarding microcopy ready for UI implementation.
- Microcopy strings
- Error message copy
- Empty state and CTA text
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
- 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
Related skills
FAQ
What UI elements does ux-writing cover?
ux-writing covers microcopy, error messages, empty states, CTAs, tooltips, form labels, placeholders, and onboarding text. The skill targets in-app copy that helps users complete tasks and understand status clearly.
How should ux-writing handle error messages?
ux-writing error messages state what happened in plain language, briefly explain why when helpful, and tell users how to recover. The skill avoids technical jargon that blocks non-engineer users from fixing issues.
Is Ux Writing safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.