ux-copy

UX Copy

Write and review UX microcopy — the small but high-leverage words inside an interface that guide users, prevent errors, and set tone. Produce copy that is clear, concise, and centered on the user's goal, then write it into the relevant components when editing code.

When to use

Trigger on requests like: "write copy for [element]", "what should this button say", "review this error message", "empty state copy", "onboarding text", "confirmation dialog wording", "rename this CTA", "is this microcopy clear", "tone of this message". Use it both to author new copy and to critique and rewrite existing copy.

Scope

UX copy covers all the in-product text users read while doing things:

• Buttons & CTAs — the action labels that drive the interface.
• Form labels & helper text — what to enter and how.
• Error & validation messages — what went wrong and how to fix it.
• Empty states — what's missing and what to do about it.
• Success / confirmation messages — acknowledging that an action worked.
• Onboarding & tooltips — orienting new users without overwhelming them.
• Confirmation dialogs — especially for destructive or irreversible actions.
• Notifications — timely, relevant, dismissible.

Principles

1. Clarity over cleverness. A user mid-task wants to understand, not be entertained. Cut wit that costs comprehension.
2. Lead with the user's goal. Frame copy around what the user is trying to do, not what the system is doing. "Find your order" beats "Order lookup module."
3. Be concise. Remove words that don't add meaning. Front-load the important part so it survives a glance.
4. Use plain language. Avoid jargon, internal terms, and acronyms. Write for the least familiar user who still belongs in the audience.
5. Use specific verbs in CTAs. Name the action: "Save changes," "Send invite," "Delete project" — not "Submit," "OK," or "Yes." The button should make sense read on its own.
6. Keep terminology consistent. Pick one word per concept (e.g., "delete," not "delete/remove/trash") and use it everywhere.
7. Sentence case by default. "Save changes," not "Save Changes" and not "SAVE CHANGES." Reserve other casing only if the project's style demands it.
8. Stay accessible. Don't rely on copy alone to carry meaning that color, icon, or layout should also convey. Write labels and messages that make sense to a screen reader read in isolation; ensure interactive elements have meaningful accessible names.