UX Copy Refiner

Say this to activate the skill

---
name: ux-copy-refiner
description: Refines microcopy in forms, buttons, modals, and error messages whenever UI strings need to be clearer or drop-offs point to confusing copy.
---

This skill rewrites UI strings so users instantly understand what happens next and what to do.

## When this skill activates
- Someone asks to rework form copy, CTAs, or error messages, or to make them easier to understand.
- A flow such as signup or checkout suffers from drop-offs and the copy should be audited as a likely cause.
- While building or reviewing UI, generic strings show up such as "Submit", "Invalid input", or an "OK/Cancel" pair.

## Workflow
1. Inventory every string in the flow in a table: element type (button, label, placeholder, helper, error, modal, empty state), current text, and where it appears.
2. Pin down voice: derive tone and form of address from the existing strings, record fixed terms in a mini glossary. Flag conflicts as open questions instead of guessing.
3. Buttons and CTAs: verb first, name the outcome of the click ("Request demo" instead of "Submit"), 2 to 4 words, never "OK", "Send", or "Click here".
4. Labels and helper text: labels are short nouns, helper text answers "why do you need this" or shows the format. Placeholders only carry format examples and never replace labels, because they vanish while typing.
5. Error messages follow the three-part formula: what happened in plain words, what the user does now, optionally why. No blaming, no bare error codes.
6. Modals: the title states the consequence ("Discard draft?"), buttons echo the action ("Discard" / "Keep editing"), never two vague options.
7. Empty states explain why nothing is here and offer exactly one next action.
8. Consistency pass: one term per concept, one form of address, one capitalization style.
9. Read-aloud test: cut filler words, move the key information to the front of the sentence.

## Output format
A Markdown table with four columns: Element, Before, After, Rationale (one sentence). Followed by open questions (tone, legal, missing context) and the mini glossary. Group by screen when there are more than 20 strings.

## Quality rules
- Every button starts with a verb and names the outcome of the click.
- No error message ships without a concrete next step.
- Placeholders never carry required information.
- One concept gets exactly one word across the whole flow, no synonym variation.
- The form of address is identical in every string.
- Jargon and error codes only appear with a plain-language explanation next to them.
- Helper text is at most one sentence.

Share this skill