ux-writing · owl-listener — Claude Code skill: interface copy that works
Writes microcopy, error messages, empty states and CTAs. Useful when the words themselves are the deliverable.
npx skills add Owl-Listener/designer-skills --skill ux-writing -a claude-codeWhat ux-writing does
The skill puts your agent in the role of an interface copywriter. It splits the work into categories: button labels, form labels, tooltips, placeholder text, error messages, empty states, confirmation messages, onboarding copy and calls to action. Each category carries its own rules — placeholder text, for instance, should show an example format rather than an instruction.
Everything lives in a single SKILL.md file with principles and checklists. Voice and tone are kept apart: brand voice stays fixed, tone shifts with context, whether that is a celebration, an error or a plain instruction. The writing principles are blunt — clear over clever, concise over comprehensive, helpful over promotional.
The skill advises writing copy before designing the UI and keeping a terminology dictionary. It also asks you to think about translation and localization from the start, because idioms and abbreviations break in other languages. For content structure and ownership questions the author points to a separate skill, content-strategy from ux-strategy.
What it helps with
- turn a technical error code into a message a user can act on
- fill an empty screen with an explanation and a button
- rewrite button labels so they name the action
- keep onboarding to one concept per step
- catch jargon and idioms before localization
Example prompts for the agent
- Rewrite the signup screen copy: labels, placeholders and the button text.
- Write an error message for a failed payment: what happened and what to do next.
- Draft an empty state for the projects list with a clear call to action.
How to install ux-writing
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill ux-writing -a claude-code2Manually: put the files in place
~/.claude/skills/ux-writing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ux-writing/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill ux-writing -a codex2Manually: put the files in place
.agents/skills/ux-writing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill ux-writing -a cursor2Manually: put the files in place
.cursor/skills/ux-writing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills ux-writing2Manually: put the files in place
.github/skills/ux-writing/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill ux-writing -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path designer-toolkit/skills/ux-writingManually: put the files in place
.devin/skills/ux-writing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill ux-writing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ux-writing
How do I install ux-writing in Claude?
Run npx skills add Owl-Listener/designer-skills --skill ux-writing -a claude-code. The skill lands in ~/.claude/skills/ux-writing/SKILL.md.
What does ux-writing do?
It guides the agent through writing interface copy: button labels, form labels, tooltips, error messages, empty states, confirmations, onboarding and CTAs. Each category has its own rules.
How is ux-writing different from content-strategy?
ux-writing handles the words inside the interface. Content structure and ownership go to the content-strategy skill from ux-strategy.
Source text
SKILL.md · MIT
--- 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
© Owl-Listener · MIT · Owl-Listener/designer-skills
Similar skills
Everything for Design →ux-writing by other authors comes first.