UX Writing Generator

Why microcopy is the highest-leverage thing you can rewrite

The smallest words on a screen do the heaviest lifting. The button label decides whether someone presses. The error message decides whether they recover or abandon. The empty state decides whether they understand what to do next. And yet microcopy is the thing teams most often hand to whoever's available, with no brief, at the end of a sprint.

Three things separate microcopy that ships well from microcopy that ships and gets quietly rewritten:

1. Specificity. "Try again" is what you write when you don't know what went wrong. "Try a different card" is what you write when you do.
2. Tone matched to moment. A playful voice in a payment failure feels disrespectful. A calm voice in a celebratory moment feels cold. The same product needs different tones at different points in the journey.
3. Plain language. Most teams write at grade 12. Most users — including specialist users in a hurry — read at grade 8–10. The more technical your domain, the more important plain language becomes, not the less.

The four tones in this generator

The tool exposes four tones because most microcopy decisions sit on this axis:

• Calm & clear — measured, neutral, reassuring. Default for finance, healthcare, anywhere stakes are high.
• Warm & helpful — friendly, contractions, one human touch. Default for productivity, social, education.
• Direct & expert — terse, confident, no padding. Default for tools where the user has expertise and time matters (developer tools, professional dashboards).
• Playful — light, brief wit. Use sparingly. Never at the user's expense and never in failure states.

Reading age, briefly

The Flesch-Kincaid grade level approximates the school grade a reader would need to understand a passage. Public-facing UK government writing aims for grade 9. The BBC News website averages grade 9–10. The Sun newspaper writes around grade 6.

For consumer products, grade 8–10 is usually right. Below grade 8 risks sounding patronising; above grade 12 actively excludes a meaningful share of your users — including time-pressed, distracted, multilingual, or low-vision users who all benefit from simpler structure regardless of their education level.

Three rules the generator follows

Never blame the user

"You entered an invalid email" is technically correct. "We didn't recognise that email format" is the same information without the implicit accusation. The model is trained to avoid the first construction in error messages.

Be specific about the action

Generic CTAs ("Get started", "Continue", "Submit") are weak. They tell the user a button exists but nothing about what it does. The generator favours specific verbs ("Start with £5", "Open your first pot", "Begin in under a minute"). When you're given multiple variants, the picked default is usually the most specific one.

Distinct variants, not paraphrases

If you ask three writers for empty-state copy, you get three different angles — one focuses on what's missing, one on the next action, one on the user's likely emotion. The model is asked to do the same. If the variants come back too similar, regenerate.

How to use the output

1. Read each variant out loud. Microcopy that reads natural-aloud is microcopy that reads natural-on-screen.
2. Test against the worst case. Imagine the user is angry, distracted, or doesn't speak English as a first language. Does the copy still land?
3. Don't ship the first variant uncritically. The picked default is a starting point. Edit it for your product's voice, your tokens, your specific context.
4. Pair it with the contrast checker. Beautiful copy in illegible contrast is wasted.