ux-writing
owl-listener/designer-skills
Write clear, helpful interface copy that guides users through your product.
What is ux-writing?
UX Writing helps you craft microcopy, error messages, empty states, and CTAs that reinforce product voice and user confidence. Use this when the words themselves are the deliverable—for broader content strategy and ownership, use content-strategy instead.
- Write action-oriented button labels, form labels, and tooltips
- Craft error messages that explain what happened, why, and what to do next
- Create empty-state copy that encourages users to take action
- Write confirmation messages with undo options for reversible actions
- Develop onboarding copy that introduces concepts without overwhelming
- Design CTAs that match user intent and start with clear verbs
How to install ux-writing
npx skills add https://github.com/owl-listener/designer-skills --skill ux-writingHow to use ux-writing
- 1.Define your product voice: brand personality, vocabulary, and perspective
- 2.Identify the copy categories you need (microcopy, errors, empty states, CTAs, onboarding)
- 3.Write copy before designing the UI layout (content-first approach)
- 4.Create a terminology dictionary to ensure consistency
- 5.Test your copy with real users and iterate
- 6.Consider translation and localization requirements from the start
Use cases
- Writing a complete set of UI microcopy for a new feature launch
- Rewriting error messages to be more helpful and less technical
- Creating empty-state messaging for a new section of your app
- Developing onboarding flows that guide users through key concepts
- Establishing voice and tone guidelines across your product
- Product designers and design leads
- Content strategists focused on interface copy
- Product managers defining user-facing messaging
- UX researchers testing copy with users
- Teams building voice and tone standards
ux-writing FAQ
Use ux-writing when you're writing specific interface copy (buttons, errors, tooltips). Use content-strategy for broader content structure, ownership, and information architecture.
Write copy first. Content-first design ensures the words drive the layout and interaction, rather than fitting words into a pre-designed interface.
Use a human tone, explain what happened clearly (not technically), briefly explain why if helpful, and provide a specific next action. Avoid words like 'invalid' or 'failed.'
Start with a verb, be specific about the outcome (not just 'Click here'), match what the user wants to do (not what the business wants), and make the primary CTA the most common action.
Create a terminology dictionary, document your voice and tone guidelines, and test copy with real users to catch inconsistencies early.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: ux-writing
description: Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use content-strategy (ux-strategy).
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
More from owl-listener/designer-skills and the wider catalog.
version-control-strategy
Define versioning strategy for design files, components, and libraries to keep collaboration organized and traceable.
visual-hierarchy
Establish visual hierarchy through size, weight, color, spacing, and position to guide user attention.
von-restorff-effect
Make one element stand out by differentiating it from its surroundings to capture attention and memory.
wireframe-spec
Specify wireframe layouts with content priority, component placement, and interaction annotations.
migrate-oxfmt
Migrate your JavaScript/TypeScript project from Prettier or Biome to Oxfmt with automated config conversion.
migrate-oxlint
Automated migration guide from ESLint to Oxlint, a high-performance Rust-based linter.