Ux Writing

owl-listener/designer-skills/designer-toolkit/skills/ux-writing

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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

AI-generated overview

Guides writing of interface copy such as microcopy, error messages, empty states, and CTAs.

What it does
This skill provides instructions for writing clear, helpful user interface copy that guides users and reinforces product voice. It covers microcopy, error messages, empty states, confirmation messages, onboarding copy, and calls to action, along with voice and tone guidance and writing principles. It produces written interface text rather than files or code.
When to use it
Use it when the words themselves are the deliverable, such as labeling buttons and forms, drafting error or confirmation messages, or writing empty-state and onboarding copy. It is not intended for content structure or ownership decisions.
Requirements
None beyond the agent; it is instructions only and ships no scripts.

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

Source and attribution

Source:owl-listener/designer-skillsindesigner-toolkit/skills/ux-writingat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Ux Writing · designer-toolkit/skills/ux-writing Agent Skill | SourceWeft