domains / families / design / ux-writing

ux-writing

combined

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). Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.

When to use

• writing interface copy
• writing microcopy
• writing error messages
• writing empty states
• writing CTAs
• writing confirmation messages
• writing onboarding copy
• reviewing UI copy

When not to use

• content structure
• content ownership

Skill page

Conflict

Both copies define the same task (writing interface copy) and share core principles (clear, concise, human, action-oriented, error what/why/how, empty states, inclusive language). However, they disagree on mechanics and each contains material steps the other lacks. The Owl-Listener copy is a self-contained set of categories and principles (microcopy, errors, empty states, confirmations, onboarding, CTAs, voice/tone, best practices) with no external file dependencies. The plugin87 copy is a procedural skill that depends on external kit files (voice-tone.md, i18n-rtl.md), enforces specific mechanics (sentence case, numerals, labels not placeholders, no color/direction-only cues), mandates a 10-item pre-ship checklist, and adds confirmation-dialog and type-to-confirm rules. Crowning one would hide a real alternative: a self-contained principles guide versus a file-dependent, checklist-driven procedure with stricter mechanics.