PannKs
UsefulTools & notes

Library

OverviewShort links
Prompts5
  • Code Review Partner
  • Bug Report Rewriter
  • SEO Blog Outline
  • Commit Message Writer
  • UI Microcopy Rewriter
How To4
← All Prompts

UI Microcopy Rewriter

Rewrites buttons, empty states and error messages so they say what happens next — with three options per string, not one.

tags
designwritingux
model
any
updated
2026-08-13
prompt.txt
You are a UX writer. Rewrite the interface strings below.

Product: {{product}}
Who reads this: {{audience}}
Voice: {{voice}}
Language: {{language}}

For each string give three options:
A — plain and short
B — warmer, one degree more human
C — the shortest thing that still works

Then one line: which you would ship, and why, in under 20 words.

Rules for every option:
- Say what happens next, or what the reader can do about it. Never only what
  went wrong.
- No blame ("you entered an invalid..."), no dead ends ("an error occurred").
- Error messages name the fix, not the exception.
- Buttons start with a verb and describe the outcome, not "Submit" / "OK".
- Empty states say what this space will hold and how to put the first thing in it.
- Respect the character budget if one is given; otherwise keep buttons under
  24 characters and messages under two lines.
- Write in {{language}}. Do not translate product names or literal UI labels
  that appear elsewhere in the app.

Strings:
{{paste_strings_here}}

Loading…

← NewerCommit Message Writer
Buy Me A Coffee

v.4.0.0 | Created By Next.JS 16.3.1

Pann Kaansadich © 2026

When to use

Any time a screen is finished but reads like it was written by the database. Especially good on error states, which is where default copy hurts most.

Fill in

  • {{product}} — one line on what the app does
  • {{audience}} — e.g. first-time users, non-technical
  • {{voice}} — e.g. calm, direct, no exclamation marks
  • {{language}} — e.g. Thai or English
  • {{paste_strings_here}} — one string per line, with the context in brackets

Example

Input

[error, after failed upload] An error occurred. Error code 413.
[empty state, projects list] No data.
[button, checkout] Submit

What comes back (excerpt)

An error occurred. Error code 413. A — That file is too large. Try one under 10 MB. B — That one didn't fit — files need to be under 10 MB. Want to try another? C — File too big (max 10 MB) Ship A — names the limit and the next action without a second sentence.

No data. A — No projects yet. Create one to get started. B — This is where your projects will live. Add the first one whenever you're ready. C — No projects yet Ship B — an empty first-run screen is where a little warmth pays off.

Submit A — Place order B — Place your order C — Place order Ship A — says what the click does; "Submit" says what the form does.