← LeaderboardThe Skill Leaderboard

ux-writing

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

Published by Owl-Listener ↗Owl-Listener/designer-skills

Try your first task

ux-writing

Start a fresh conversation. Replace the highlighted placeholders.

Use ux-writing to write clear, accessible UI copy for [user flow], including [error states] and confirmation messages, aligned to [product voice].

Required inputs

  • [user flow]
  • [error states]
  • [product voice]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: ux-writingdescription: 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