Skip to content
Marketplace

ux-writing

by owl-listener

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).

Overview

SKILL.mdRead at 9a6930c

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

Files 1 file

Install it by hand

Deska runs this for you, for every agent you pick. To run it yourself in a terminal:

npx skills add owl-listener/designer-skills --skill ux-writing

More from owl-listener

  • presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,800 installs on skills.sh0
  • typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,300 installs on skills.sh0
  • visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,300 installs on skills.sh0
  • color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,200 installs on skills.sh0
  • dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,200 installs on skills.sh0
All skills by owl-listener