ChatGPT Prompts for UX Writing
Write microcopy for [real interface element, e.g. "a button that submits a form"]. Real user state at this moment: [real context]. Real tone: [real tone, e.g. "friendly but efficient"].
ChatGPT prompts for UX writing work from a real specific interface moment and real user intent — microcopy for a real button, error message, or onboarding flow — not generic interface text, since UX writing lives or dies on real specific context and real user state.
What this produces
Microcopy written for a real specific interface moment, an error message that’s clear and genuinely helpful rather than technical or vague, and onboarding copy that respects a real new user’s actual state of knowledge. Interface text grounded in real context, not generic UI copy.
Variations
Three ready-to-copy versions for UX writing tasks.
Write microcopy for {real interface element, e.g. “a button that submits a form”}. Real user state at this moment: {real context}. Real tone: {real tone, e.g. “friendly but efficient”}. Keep it real short.
Write an error message for {real error scenario}. Real cause: {real cause}. It should be genuinely clear and helpful, not technical jargon, and tell the user a real next step if possible.
Write onboarding copy for {real product/feature}. Real user’s actual starting knowledge: {real level, e.g. “brand new, no context”}. Real key thing they need to understand first: {real key point}.
FAQ
How short should microcopy really be?
As short as clarity allows — UX writing generally favors brevity, though never at the cost of a user genuinely understanding what to do.
Should error messages ever include technical detail?
Generally lead with clear, human language and a real next step — technical detail can be included secondarily for advanced users or support purposes, but shouldn’t be the primary message.
How do I write for users at very different experience levels?
Consider whether your real interface needs different copy paths for new versus returning users, since one-size-fits-all copy often serves neither well.
Can this help with a full onboarding flow, not just individual screens?
Yes — describe the real sequence and real key points for each step, and the same principle of matching real user state applies across a flow.
