Prompts / microcopy_review
UX writing and microcopy review Free
Reviews buttons, errors, empty states and other interface text for clarity, tone and consistency, and removes the AI-writing tells.
Run it
- Claude Code:
/mcp__designers__microcopy_review - Claude Desktop and claude.ai: plus menu, Add from Designers, UX writing and microcopy review
- Any app: Use the microcopy_review prompt from the Designers server on the strings, or a figma link to pull text from.
Arguments
| Name | Meaning |
|---|---|
copy * | The strings, or a Figma link to pull text from |
voice | Brand voice in a few words, if there is one |
audience | Who reads it, and in what state of mind |
* required
What your assistant is told to do
The full instructions, so you can see exactly what you are asking for:
Review interface copy as a UX writer. The aim is that a person in a hurry does the right thing, and that the product sounds like people made it.
Copy: <copy>
Voice: <voice>
Reader: <audience>
Method:
1. If given a Figma link, pull every text layer (If the input is a Figma link: parse it (figma.com/design/:fileKey/..., node-id=1-2 means nodeId "1:2"), call get_metadata to see the frames, get_screenshot for each frame you will judge, and get_design_context for layout, text and tokens. Read the picture before the code. If the Figma tools are not connected, say so and ask for screenshots or exported frames instead; do not guess at what is in the file.) and label each with its role: button, error, empty, tooltip, placeholder, heading, toast, label, body.
2. Call review_ui_copy with the strings, one per line, prefixed with the role. Use its findings as a starting point; add what a human reader would catch.
3. Read resource designers://reference/slop-tells for the writing tells and fix any you find.
4. For each string that needs work, give the original, the problem in one line, and a rewrite. Rewrites follow these rules: buttons name the outcome in one to three words; errors say what happened and what to do, never blame, never "Oops"; empty states say what lives here and give the next action; tooltips stay under about 15 words; no "successfully"; sentence case unless the brand says otherwise; consistent words for the same action everywhere (pick Sign in or Log in); no exclamation marks except where delight is earned.
5. Report the set-level problems separately (inconsistent terms, mixed casing, error tone).
6. Offer a short voice sheet: three adjectives, one do and one do not each, taken from what the existing good strings already do.
Write the rewrites as a person would speak. Avoid the AI tells: triads in every list, "not just X but Y", em-dashes, tidy closing lines.