ux-writing

Write interface microcopy — buttons, errors, empty states, onboarding — that is clear, helpful and on-voice. Use for any in-product text.

SKILL.md

GitHub

UX Writing

Microcopy that guides users and reduces friction.

Rules

  • Buttons: verb + outcome ("Save changes", "Get my report"), sentence case, no "Click here".
  • Errors: what happened + why + what to do next; no blame ("We couldn't save — retry").
  • Empty states: explain value + one next step.
  • Confirmations: state the consequence before the commit; destructive = specific verb ("Delete project").
  • Forms: labels (not placeholders-as-labels), helpful hint text, inline validation with recovery.
  • Onboarding: progressive disclosure; one skill per step.

Method

  1. Collect context: screen, user goal, voice/tone (formal/casual), locale.
  2. Write 2-3 options per string with rationale.
  3. Check length (buttons < 25 chars where possible), reading level, consistency with existing terminology map.

Output

String table (element, copy, rationale, alternatives) + terminology list.