BlogAI

Prompting AI for UI Copy: 10 Patterns That Cut the Generic

Ten prompt patterns a designer can use to get UI copy that fits the screen, the user and the product instead of generic AI filler.

Denny Pratama

18 Nov 2026 · 5 min read · AI

Prompting AI for UI Copy: 10 Patterns That Cut the Generic

Ask an AI tool for "button text for a signup form" and you'll get something pleasant and forgettable. "Get Started." "Join Now." "Unlock your potential." None of it is wrong. None of it knows your product either.

The fix is rarely a better model. It's a better prompt. Below are ten patterns I'd use when asking AI for interface copy. They're opinions and reasoning, not test results, so adjust them to your product.

01Give the model the screen, not the string

1. Describe the moment

Say who the user is, what they just did and what they want next. Compare two prompts:

  • "Write an error message."
  • "A user uploaded a CSV to import contacts. Three rows failed because the email column was empty. Write the error message shown above the results table."

The second gives the model facts to work with. The output will mention rows, emails and a next step, because you gave it those things.

2. State the constraints up front

UI copy lives in small boxes. Tell the model the limits: "Button label, max 20 characters." "Toast message, one sentence, no more than 60 characters." If you skip this, you'll get paragraphs where you needed a few words.

3. Name what happens next

Good copy often just describes the outcome. Include it: "Clicking this sends an invoice email to the client and locks the invoice for editing." The model can then write a label that says so, which is the same logic I described in Microcopy on Buttons: Why "Submit" Is Rarely the Right Label.

02Control the voice

4. Paste a short voice guide

Five or six lines is enough:

  • Plain words, no jargon.
  • Address the user as "you."
  • No exclamation marks.
  • Say "Save," not "Submit."
  • Never blame the user.

Reuse it in every prompt. This is the cheapest consistency tool I know of.

5. Give two or three real examples

Examples beat adjectives. "Friendly but professional" means different things to different people, and to a model. Paste a few strings you already like from your product and say "match this tone." If your product is new, write two strings by hand first.

6. Ban the filler words

Models drift toward certain phrases: "seamlessly," "unlock," "empower," "oops!" Add a line such as "Do not use: seamless, unlock, empower, oops, supercharge." It's blunt, and it works because you're removing the usual defaults.

03Ask for options, then judge them

7. Request variants with a reason

Ask for five versions and one line on how each differs: shorter, more formal, more specific. Seeing the range helps you notice what you actually want. You pick; the model doesn't.

8. Ask it to critique your draft instead

Sometimes the better move is to write the copy yourself and paste it in. Prompt: "Here's my error message. Point out anything vague, blaming or too long. Don't rewrite it." You keep authorship, and you get a second reader.

04Check what the model can't know

9. Verify every factual claim

AI will happily write "Your data is encrypted" or "This usually takes 2 minutes" if it sounds right in context. It has no idea whether that's true for your product. Say a password reset screen says "Check your inbox, the link expires in 24 hours." Someone has to confirm the 24 hours with whoever built it. Anything about time, security, billing, cancellation or privacy needs a human check.

10. Test the copy in the real layout

A string that looks fine in a chat window can fail in the interface. Put it into the actual component and check:

  • Does it wrap awkwardly at a narrow width?
  • Does it still make sense without the surrounding paragraph?
  • Would a longer translation break the layout?
  • Does a screen reader user get the same meaning from the text alone?

If you're building the screen yourself with AI tools, this is the step that's easiest to skip, since the code "works." Long strings are also a common cause of shifting layouts, which I covered in Layout Shift From a Designer's Side: Images, Fonts, Embeds.

05A prompt template you can steal

Here's a starting point that combines most of the patterns:

You're writing UI copy for [product type]. Voice: [your five lines]. Avoid: [banned words].

Screen: [what the user sees]. The user just [action]. Next, [outcome].

Write [component, e.g. an inline error] in [max characters]. Give 4 options and one line on how each differs. Flag anything that makes a factual claim I need to verify.

The last line matters. It asks the model to point at its own risky claims, so your review time goes where it counts. It won't catch everything, so you still read every word.

06Where I'd draw the line

I'd use AI freely for first drafts, variants, tone checks and tedious sets like twenty validation messages. I'd be careful with anything legal, anything involving money, and any copy that makes promises about behavior.

I'd also never ship a string I haven't read in context. The model writes quickly, but the responsibility for what the interface says to a real person stays with the designer.

Start small: pick one screen, write the context and constraints, and compare the result to what you'd have written alone. If the prompt does its job, the copy will sound like your product and not like every other one.

07Frequently asked questions

Should I let AI write all the UI copy in my product?

I wouldn't. AI is good for producing options and first drafts quickly, but it doesn't know your users, your legal constraints or your product's actual behavior. Treat its output as a draft that a person who understands the product has to approve.

What is the most important thing to include in a UI copy prompt?

Context about the screen: who the user is, what they just did, and what happens next. Without that, the model fills the gap with generic, friendly-sounding text. Add the character limit and the tone rules and the results improve a lot.

How do I keep AI-written copy consistent across screens?

Write a short voice and terminology guide and paste it into every prompt. Include preferred words, banned words and two or three example strings. Then review the finished screens side by side to catch drift.

AI

Denny Pratama

Product designer in Indonesia. Since 2018 I’ve designed SaaS products, dashboards and marketing sites, and now I build my own designs too.

About me