domains / design / ux-copywriting / ux-writing

ux-writing

Skill card

combined

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.

Repositories

Other copies

Combined skill

# UX Writing

Write or review interface copy (microcopy, error messages, empty states, confirmations, onboarding, CTAs) in the product's voice.

## Steps
1. If a voice-tone reference file is available (e.g., `voice-tone.md`), read it for voice principles, tone spectrum, formulas, and inclusive-language rules. If no reference file is available, proceed with the principles below.
2. Match tone to the user's emotional state (onboarding, success, routine, error, destructive). Higher stress → plainer language.
3. Apply the following formulas:
   - **Buttons/CTAs:** Frontload the verb, name the outcome. Be specific about the outcome. Match user intent, not business intent. Primary CTA should be the most common action.
   - **Confirmation dialogs:** The confirm button restates the action and object (e.g., "Delete account", not "Delete"/"OK"/"Yes"). The title asks ("Delete account?"), the button answers in matching words. Cancel stays "Cancel". For irreversible/high-stakes actions, require a type-to-confirm step.
   - **Errors:** What happened → why (if helpful and brief) → how to fix. No dead ends, no codes/stack traces. Use a human tone, not robotic or blaming.
   - **Empty states:** Explain what will appear here → guide the user to take a first action. Use an encouraging, helpful tone. Provide a clear CTA.
   - **Onboarding:** Welcome without overwhelming. One concept at a time. Action-oriented. Allow skipping.
   - **Form labels:** Clear, concise, no jargon. Use labels, not placeholders, for input fields. Placeholder text, if used, should show example format, not instructions.
   - **Tooltips:** Brief explanations for complex features.
4. Enforce mechanics:
   - Sentence case (no ALL CAPS).
   - Use numerals, not spelled-out numbers, where appropriate.
   - No blame on the user.
   - No directional or color-only instructions (accessibility).
   - Inclusive language; avoid jargon, abbreviations, and idioms.
5. Run a pre-ship copy checklist:
   - Reads naturally aloud; frontloaded verb on actions; no jargon/blame/dead-ends.
   - Errors follow what→why→how; empty states give value→action; no bare "No data"/"Error".
   - Mechanics: sentence case, numerals, labels (not placeholders), no color/direction-only cues, inclusive language.
   - Within character limits for tight UI.
   - Translatable (no string concatenation; consider localization from the start).
   - Consistent with brand voice and terminology dictionary.
   - Tested with real users where possible.

## Output
Final copy (or a redline review) that reads naturally aloud and passes the checklist. Keep within any character limits for tight UI.

## Conflicts
- **Owl-Listener/designer-skills** recommends placeholder text as example format; **plugin87/ux-ui-agent-skills** enforces labels (not placeholders). The combined instruction allows placeholders for example format but requires labels for input fields.
- **plugin87/ux-ui-agent-skills** mandates sentence case, numerals, and a 10-item checklist; **Owl-Listener/designer-skills** does not. The combined instruction includes these as enforced mechanics and checklist items.
- **plugin87/ux-ui-agent-skills** depends on external kit files; **Owl-Listener/designer-skills** is self-contained. The combined instruction treats the reference file as optional and falls back to the principles above.