---
name: ui-micro-copy-writer
description: "Short interface copy for buttons, errors, empty states, and tooltips that tells people what happened and what to do next, in the product's own voice. Use when a designer or product writer needs button labels, error messages, empty states, or tooltips for a specific screen. Do not use for long-form marketing copy or product documentation. Related topics: design, ux, micro."
---

# UI Micro-copy Writer

Short interface copy for buttons, errors, empty states, and tooltips that tells people what happened and what to do next, in the product's own voice.

## When to use

Use this skill when a designer or product writer needs button labels, error messages, empty states, or tooltips for a specific screen. Do not use it for long-form marketing copy or product documentation.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Read the screen situation and the user's goal, and restate in one line what the user needs to know next.
3. Draft two options for each requested copy type, one tight and one warmer, matching the stated voice and moment tone.
4. Check every piece against the chosen rules, done when no error blames the user and every button starts with a verb.
5. Note length limits and localisation risks beside each piece.
6. Flag any case where the interface, not the wording, is the real problem.

## Inputs

- **Product type** (choose one: Web app, Mobile app, SaaS dashboard, E-commerce, Marketplace, Other)
- **Brand voice** (choose one: Friendly and conversational, Professional and clear, Witty and playful, Minimal and direct)
- **Audience** (choose one: Non-technical consumers, Business users, Developers)
- **Copy types needed** (choose any: Primary button labels, Secondary button labels, Empty states, Error messages, Success messages, Tooltips, Onboarding instructions, Form labels and placeholders, Warning confirmations, 404 or error pages)
- **What is happening on screen** (longer free text)
- **What the user is trying to do** (free text, e.g. "Their goal in this moment")
- **Tone for this moment** (choose one: Helpful, Reassuring, Motivating, Apologetic, Clear and direct)
- **Rules to apply** (choose any: Active voice, Be specific, Avoid negative framing, Say you not the user, Keep it short, Lead with the action or benefit)

## Output

A table or list by copy type with two options each, followed by short notes on length, localisation, and any UI changes recommended.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### UI Micro-copy

Write the UI micro-copy described below.

- Product type: {{Product type}}
- Brand voice: {{Brand voice}}
- Audience: {{Audience}}
- Copy types needed: {{Copy types needed}}
- What is happening on screen: {{What is happening on screen}}
- What the user is trying to do: {{What the user is trying to do}}
- Tone for this moment: {{Tone for this moment}}
- Rules to apply: {{Rules to apply}}

For each copy type, give two options: one tight version and one with a little more warmth. Errors say what went wrong, why if known, and the next step, never just blame the user. Empty states point to the first useful action. Button labels start with a verb that names the outcome. Add a short note on character limits and anything that needs to be localised. Flag where the screen itself should change instead of the copy.

## Pitfalls

- Writing errors that state the failure but not the next step, leaving the user stuck.
- Using the same cheerful tone for a destructive confirmation, which hides the stakes.
- Writing generic labels like Submit or OK that do not name the outcome.
