UX Write: an AI-powered UX text generator

Live at uxwrite.com

UX Write generates interface copy from a description of a UI scenario. Tell it what the screen does, who is looking at it, and what needs to happen next, and it returns multiple options across different tones, audiences, and action types. It is built for the moments UX writers actually face: the error message that has to be honest without being alarming, the empty state that has to explain and invite at the same time, the button label that has to fit the space and still mean something.

Why I built it

Most AI writing tools give you one answer, and it reads like it. Good UX text is never one answer. The same confirmation dialog needs different words for a consumer banking app and an internal admin tool, and different words again depending on whether the action is reversible. The interesting problem was not getting a model to produce copy. It was encoding the judgment that separates usable copy from filler: when to lead with the action, when reassurance matters more than brevity, how tone shifts with the stakes of what the user is about to do.

That judgment lives in the prompts and system instructions that drive the tool. Writing them was a content design exercise before it was an engineering one. I had to make my own instincts explicit, turn "this sounds wrong for an error state" into rules a model could follow, and test the output against what I would have written myself.

What I learned

The project confirmed something my research keeps showing: with AI systems, the writing is the product. My study Tokens Not Jokin' measured how content structure affects AI output quality across more than 21,000 tests, and the format of the input mattered over ten times more than the choice of model. UX Write is the same finding in miniature. The model is interchangeable. The instructions, the constraints, and the examples are where the quality comes from, and those are writing artifacts.

A note on the obvious question. A tool like this does not replace UX writers, for the same reason a style guide does not replace editors. It produces options; someone with judgment still has to pick one, and the tool is only as good as the judgment written into it. I built it to see how much of the craft could be made explicit. The answer so far is a useful amount, and nowhere near all of it.

Try it at uxwrite.com.