Skip to main content
skill CX Codex

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill ux-writing -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/ux-writing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ux-writing/

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.

ux-writing content-designer Writes and edits button labels, error messages, notifications and empty states against four standards: purposeful, concise, conversational, clear. CX Codex +1 2,700installs ux-writing plugin87 Write or review interface text, from button labels to errors and empty states. The skill applies a project’s voice and checks copy against a pre-ship checklist. CX Codex +1 517installs writing-for-interfaces andrewgleave Guides UI text drafting, error message rewrites, and button labels to keep interface copy aligned with product voice. CX Codex +1 1,100installs ux-writing-content-design hueyexe Writes and critiques interface text: button labels, hints, empty states, errors, onboarding. Useful when the layout is done but the wording is not. CX Codex +1 562installs articulate ghaida Designs the words in a product: labels, errors, empty states, onboarding, tooltips. Use it when the copy is the problem, not the layout. CX Codex +1 2,700installs clarify aladicf Rewrites labels, error messages, empty states and CTAs so users know what happened and what to do next. CX Codex +1 533installs better-writing jakubkrehel Writes and reviews UI copy, from button labels to errors and empty states. It keeps product vocabulary consistent and guides users to the next step. CX Codex +1 29,100installs brand-guidelines getsentry Applies Sentry brand and copy guidelines to user-facing text, error states, and UI flows. Useful when writing UI labels, empty states, or docs. CX Codex +1 2,500installs

From the same set109

journey-map This skill maps one persona's end-to-end experience: stages, touchpoints, emotions and pain points. Useful when you're improving something that already exists. CX Codex +1 2,100installs component-spec This skill writes a full spec for one design-system component: anatomy, variants, states, accessibility and usage rules. Useful when a library grows and the API needs pinning down. CX Codex +1 2,100installs design-principles Helps teams define actionable design principles to resolve recurring product debates. Useful when the same decisions keep getting relitigated. CX Codex +1 2,100installs accessibility-audit Audits an existing interface against WCAG and reports issues with severity, impact, and remediation steps. CX Codex +1 2,100installs critique-typography Audits typography on a rendered screen: scale usage, readability, consistency and token compliance. Useful during UI review. CX Codex +1 2,000installs version-control-strategy Defines version control strategies for design files, component libraries, and tokens. It helps teams stop chaotic file history and establish clear release routines. CX Codex +1 2,000installs critique-visual-hierarchy This skill reviews a rendered screen across four dimensions and tells you where the eye actually lands. Useful when attention goes to the wrong place. CX Codex +1 2,000installs click-test-plan Turns a findability question into a test plan: where users click first and whether they locate items in your navigation. Useful when a design is ready but untested. CX Codex +1 2,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor