ux-writing-and-microcopy

name	ux-writing-and-microcopy
description	Use when writing or reviewing buttons, field labels, hints, tooltips, menus, toggles, placeholders, tabs, navigation labels, or other routine interface microcopy. Use error-empty-and-system-messaging for system states and voice-tone-and-content-style-guide for voice governance.
metadata	{"portable":true,"category":"10-content-design-and-ux-writing","compatible_with":["claude-code","codex"]}

UX Writing & Microcopy (Clarity-First Interface Copy)

Microcopy is the small, functional text the user reads at the moment of action — the verb on a button, the label above a field, the one line in a confirmation dialog. It is where most of an interface's words live and where most of its friction hides. This skill makes that copy clear first, on-brand second, and never decorative — and ties every string back to the product's voice rather than letting each screen drift.

Microcopy is also a doctrine concern, not just a writing concern. Generic, hedged interface copy ("Submit", "Are you sure?", "Oops! Something went wrong") is the verbal form of AI slop: the convergent, unconsidered default. Per doctrine/design-doctrine.md §0–2, the moat is output that looks authored — and that includes the words. State the voice, then write copy a templating tool would never have produced.

Use When

• Deciding what a button or CTA should say (primary action, secondary, cancel, destructive).
• Writing form labels, hints, placeholders, helper text, and inline-success strings.
• Writing tooltips and short helper text for ambiguous icons or controls.