Ux Writing
Generate consistent UI microcopy, errors, empty states, and CTAs that match product voice while you ship screens.
Overview
UX Writing is an agent skill most often used in Build (also Validate landing, Grow content) that drafts and refines UI microcopy, errors, empty states, and CTAs with clear voice and tone rules.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill ux-writingWhat is this skill?
- Covers six UX writing categories: microcopy, errors, empty states, confirmations, onboarding, and CTAs
- Error message framework: what happened, optional why, specific next step, human tone
- CTA rules: verb-led, outcome-specific, aligned to user intent over business pressure
- Separates stable brand voice from situational tone across success, warning, and failure states
- 6 UX writing categories covered in the skill
Adoption & trust: 598 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your product UI works but labels are vague, errors blame the user, and empty screens do not tell people what to do next.
Who is it for?
Indie builders iterating on SaaS or app screens who need fast, consistent copy passes before release or after user confusion shows up in support.
Skip if: Long-form SEO articles, legal contracts, or brand strategy projects where a dedicated copywriter and full voice guide already lock every phrase.
When should I use this skill?
Write effective UI copy including microcopy, error messages, empty states, and CTAs.
What do I get? / Deliverables
You get revised interface copy across the six UX writing categories with verb-led CTAs, humane errors, and onboarding that can be skipped without overwhelm.
- Revised UI strings by category
- Voice and tone notes for the feature
- CTA and error message variants
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Most copy work happens while interfaces are being built, but the same skill applies when polishing flows before ship and when improving in-app messaging during growth. Frontend subphase is the canonical shelf because the skill targets in-product strings tied to components users tap and read on each screen.
Where it fits
Rewrite hero and signup CTAs so they are verb-led and match visitor intent on a landing page test.
Draft form labels, tooltips, and inline validation messages for a settings screen.
Polish confirmation and undo copy before a feature flag rollout.
Refresh lifecycle emails’ in-app counterparts so tone stays human when trials end or limits hit.
How it compares
Use for in-product strings and flows, not as a replacement for a dedicated marketing or SEO content skill.
Common Questions / FAQ
Who is ux-writing for?
Solo and indie builders who design and ship their own UI and want an agent to apply UX writing rules to buttons, forms, errors, and onboarding without hiring a separate copy specialist for every screen.
When should I use ux-writing?
Use it while building frontend flows, when tightening validate-phase landing or signup copy, before ship when reviewing error and empty states, and during grow when improving lifecycle or support-facing in-app messages.
Is ux-writing safe to install?
It is text-generation guidance with no prescribed shell or API access; check the Security Audits panel on this page and review outputs before publishing user-facing copy.
SKILL.md
READMESKILL.md - Ux Writing
# 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