| name | designing-microcopy-systems |
| description | Create scalable, consistent microcopy patterns for UI components. Use when building design systems, establishing copy standards for component libraries, or systematizing recurring UI text. |
Designing Microcopy Systems
Quick start
Collect or infer:
- Component inventory (buttons, modals, forms, toasts, etc.)
- Existing design system documentation
- Product voice and tone parameters
- Platform constraints (character limits, localization requirements)
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- Inventory all UI components that require copy.
- Categorize components by function: action, feedback, navigation, instruction, status.
- Define copy slots for each component (label, helper text, error, success, placeholder).
- Establish patterns for each slot: structure, tone, constraints.
- Document variation rules (when deviation is allowed, when it is not).
- Create usage examples showing correct and incorrect application.
- Run the rubric check. Revise until it passes.
Degrees of freedom
- Low freedom: Pattern definitions and constraint rules must be explicit and testable.
- Allowed variation: Example phrasing may adapt to product voice, as long as structural patterns remain consistent.
References