microcopy
npx machina-cli add skill Dragoon0x/Product-Skills/microcopy --openclawFiles (1)
SKILL.md
1.8 KB
Microcopy
The small words that shape big experiences.
How to use
/microcopyApply microcopy constraints to this conversation.
Constraints
Buttons
- MUST describe the action outcome, not the mechanical action
- "Create project" not "Submit". "Send invite" not "Confirm".
- Destructive actions: name what's being destroyed ("Delete project" not "Delete")
- MUST use sentence case, not Title Case or ALL CAPS
- Loading state: show progress ("Saving..." not "Please wait")
Confirmations and Dialogs
- Title: what's about to happen
- Body: what it means and whether it's reversible
- Primary button: the action being confirmed
- Secondary button: "Cancel" (not "No" or "Go back")
- NEVER use "Are you sure?" without explaining the consequence
Tooltips and Help Text
- MUST add information the user doesn't already have
- Keep under 15 words. If it needs more, use a help page.
- SHOULD answer "why" not just "what" (why this field exists, not just what to put in it)
- NEVER use tooltips as the only way to explain essential functionality
Empty and Placeholder Text
- Input placeholders: show the expected format, not the label ("name@company.com")
- MUST NOT use placeholders as labels (they disappear on focus)
- Empty search: suggest search terms or show popular queries
- NEVER use "N/A", "null", "undefined", or "—" where a human-readable message belongs
Error Micro-Copy
- MUST say what went wrong in plain language
- MUST say how to fix it
- Place error text adjacent to the field that caused it
- Use red for errors, but don't rely on color alone (add an icon or text prefix)
Source
git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/communication/microcopy/SKILL.mdView on GitHub Overview
Microcopy constrains and refines the small words that shape user experiences. It covers button labels, tooltips, confirmations, and placeholders - three-word strings that determine whether a product feels polished or unfinished. Used during any copy audit pass to ensure clarity, consistency, and purposeful messaging.
How This Skill Works
During reviews, apply the microcopy constraints to each UI element: ensure buttons describe outcomes, confirmations explain consequences, and tooltips provide why or how. Placeholders should show the expected format, empty states should suggest useful terms, and error messages should sit next to the offending field with a clear fix and an accessible cue.
When to Use It
- During a product copy audit pass to tighten button labels, tooltips, and placeholders.
- When labeling primary actions so they describe outcomes (e.g., 'Send invite' instead of 'Confirm').
- When designing confirmations and dialogs to clearly state consequences and reversibility.
- When crafting tooltips to add why a field exists, not just what to input.
- When improving error micro-copy by stating what went wrong and how to fix it, adjacent to the field.
Quick Start
- Step 1: Identify all primary actions, confirmations, tooltips, placeholders, and errors in the UI.
- Step 2: Apply microcopy constraints to each element, ensuring outcomes, reasons, and formats are explicit.
- Step 3: Validate with design QA and user testing, then iterate based on feedback.
Best Practices
- Describe outcomes for buttons, not the mechanical action (e.g., 'Send invite' rather than 'Submit').
- Name destructive actions by what gets destroyed (e.g., 'Delete project').
- Use sentence case and avoid using placeholders as labels.
- Keep tooltips under 15 words and explain why the field exists.
- Place error messages next to the relevant field and include actionable fixes; use an icon or prefix.
Example Use Cases
- Button: Create project
- Destructive action: Delete project
- Tooltip: We’ll email receipts and project updates.
- Placeholder: name@company.com
- Error: Enter a valid email address in the format name@domain.com.
Frequently Asked Questions
Add this skill to your agents
