Microcopy
Skill Dragoon0x/product-skills/skills/communication/microcopy
The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.
npx -y skills add Dragoon0x/product-skills --skill microcopyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
The small words that shape big experiences. Button labels, tooltips, confirmations, placeholders, and the 3-word strings that determine whether a product feels polished or half-finished. Use during any copy audit pass.
SKILL.md
1.8 KB, as published. Nobody here has run it
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 ("[email protected]")
- 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)