Prompts / microcopy_write
Write empty states, errors and microcopy Free
Writes the small text a product needs (empty states, errors, confirmations, tooltips, onboarding hints) in the product's voice, then checks it.
Run it
- Claude Code:
/mcp__designers__microcopy_write - Claude Desktop and claude.ai: plus menu, Add from Designers, Write empty states, errors and microcopy
- Any app: Use the microcopy_write prompt from the Designers server on the screens or situations that need copy, or a figma link.
Arguments
| Name | Meaning |
|---|---|
screens * | The screens or situations that need copy, or a Figma link |
voice | Voice in a few words, or an example line |
audience | Who reads it and how they feel at that moment |
* required
What your assistant is told to do
The full instructions, so you can see exactly what you are asking for:
Write the interface text for these situations, in a voice that sounds like people made it.
Situations: <screens>
Voice: <voice>
Reader: <audience>
1. If given a Figma link, read the frames (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 list each place that needs text with its role.
2. For each, write one primary version and one alternative. Rules: an empty state says what lives here, why it is empty, and offers the one action to fill it; an error says what happened, then what to do, never blames and never says Oops; a confirmation says what changed and, if it matters, how to undo; a tooltip is one short sentence and adds information the label does not; a button names the outcome in one to three words; the same action has the same word everywhere.
3. Keep it plain. No exclamation marks unless delight is earned. No triads in every list, no "not just X but Y", no em-dashes, no tidy closing line.
4. Call review_ui_copy on everything you wrote (prefix each line with its role) and fix every flag.
5. Output a table: place, role, copy, alternative, note. Add a four-line voice sheet drawn from what you wrote.