UX Writing with AI
AI is fast at generating microcopy — error messages, button labels, empty states, tooltips, and onboarding text — but its default output sounds like every other product. The differentiator is voice guidance: give AI a concrete style sample and specific constraints, and it produces copy worth using. Without that context, you get polished-but-generic.
Establish Voice Before Writing Anything
Every UX writing prompt should begin with a voice definition. Without it, AI defaults to a formal, helpful, slightly corporate tone that fits no product in particular.
Product: [PRODUCT NAME — e.g., "a personal finance app for people in their 20s"]
Voice: [DESCRIBE IN 3-5 CONCRETE ADJECTIVES — e.g., "direct, slightly informal, never condescending, practical, avoids exclamation marks"]
Audience: [WHO IS USING THIS — e.g., "people who find traditional banking stressful; they want to feel in control, not lectured"]
Do not use: [LIST FORBIDDEN PHRASES/TONES — e.g., "words like 'simply', 'just', 'easy'; exclamation marks; passive voice; jargon like 'leverage'"]
Voice sample (existing approved copy): "[PASTE 2-3 SENTENCES YOU HAVE ALREADY APPROVED]"
Paste this preamble at the top of every UX writing session. It takes 2 minutes to set up and saves significant editing time on AI output.
Error Messages
Error messages are the highest-value UX copy. A bad error message traps users; a good one tells them exactly what happened and what to do next.
[VOICE PREAMBLE FROM ABOVE]
Write 3 variations of an error message for this scenario:
Error: [DESCRIBE WHAT TECHNICALLY HAPPENED — e.g., "payment failed because the card was declined by the issuing bank"]
User context: [WHAT THE USER WAS TRYING TO DO — e.g., "completing a purchase for a subscription"]
Each variation must:
- State what happened (not blame the user)
- Tell them exactly what to do next
- Be under 20 words
- Not use the word "error" or "unfortunately"
After the 3 variations, explain what is different about each and when you would choose it.
The 20-word limit forces specificity. Longer error messages get skimmed and the action step gets missed.
Empty States
Empty states are conversion moments — a first-time user who sees an empty screen and understands nothing leaves. Empty states should explain what will appear here, why it is empty now, and what the first action is.
[VOICE PREAMBLE]
Write copy for an empty state in [DESCRIBE THE SCREEN — e.g., "the transactions list on a new account"].
Why it is empty: [e.g., "the user has not made any transactions yet"]
First action we want them to take: [e.g., "connect a bank account"]
Write:
- A headline (max 6 words)
- A body line explaining what will appear here and when (max 15 words)
- A CTA button label (2-4 words, action verb)
Give 2 variations: one encouraging, one matter-of-fact. Do not use "No [items] yet" as the headline.
"No transactions yet" is the most common empty state headline and the least useful. Explicitly forbid it in the prompt.
Onboarding Copy
[VOICE PREAMBLE]
Write copy for a [NUMBER]-step onboarding flow for [PRODUCT].
Steps:
1. [WHAT HAPPENS ON STEP 1 — e.g., "user enters email and password"]
2. [STEP 2 — e.g., "user connects their bank account via OAuth"]
3. [STEP 3 — e.g., "user sets a monthly spending goal"]
For each step provide:
- Screen title (max 5 words)
- Subtitle explaining WHY this step matters to the user (not what it is technically)
- Primary button label
- Skip link text (if this step is optional)
The subtitle must answer "what does the user get from doing this" not "what we need from them".
The subtitle framing (user benefit vs technical requirement) is the most common onboarding copy mistake. Making it explicit in the prompt prevents AI from defaulting to the wrong frame.
Common Microcopy Tasks
| Copy type | Key constraint to include | Common AI mistake to prevent |
|---|---|---|
| Button labels | Max word count (2-4); must start with action verb | Generic labels like "Submit", "Continue", "OK" |
| Form field placeholders | Show example value format, not label repetition | Repeating the field label as placeholder (e.g., "Email" in email field) |
| Confirmation dialogs | State what will happen, not just ask yes/no | Vague "Are you sure?" with Yes/No buttons |
| Tooltips | Max 15 words; answer "why" not "what" | Restating the label in different words rather than adding context |
| Success messages | Confirm what happened and what is next | Generic "Success!" with no next-step guidance |
Reviewing AI Copy
Good AI UX copy
- Matches your voice sample without sounding forced
- Error messages state the cause and the fix
- Button labels start with an action verb specific to the action
- Empty states explain what appears there and why it is empty now
- Onboarding subtitles frame value for the user, not requirements for you
AI copy that needs rewriting
- Uses "simply", "just", "easy", or "quickly"
- Starts error messages with "Unfortunately" or "We're sorry"
- Uses generic CTAs: "Click here", "Submit", "OK"
- Passive voice: "Your account has been created" (no next step)
- Exclamation marks on every success state: "You're all set!"
Checklist: Do You Understand This?
- Why does AI UX copy default to a generic tone — and what is the single most effective fix?
- Write a voice preamble for a security-focused enterprise tool whose audience is IT administrators.
- What three things must every error message include — and what word should it avoid?
- Why is "No transactions yet" a weak empty state headline — what makes a better one?
- How should an onboarding subtitle frame its content — user benefit or technical requirement?
- Name three AI copy red flags that signal the output needs rewriting before use.