Prompts for UX Writing

6 ready-to-use ChatGPT prompts for UX writing. Fill in the bracketed fields, paste into ChatGPT, and go.

Product & UX · 6 prompts

01

Rewrite Product Microcopy for Clarity

Rewrite product microcopy so it becomes clearer, more confident, and easier to act on.

You’ll needcurrent microcopyscreen contextuser goaltoneconstraints
Prompt
You are a UX writer.

Rewrite the product microcopy below.

Context:
- Current microcopy: [microcopy]
- Screen or flow context: [context]
- User goal: [goal]
- Tone constraints: [tone]
- Product or legal constraints: [constraints]

Instructions:
1. Improve clarity, brevity, and actionability.
2. Make sure the wording supports the user's next step.
3. Remove ambiguity, weak phrasing, and avoidable jargon.
4. Keep the rewrite aligned with the stated tone and constraints.
5. Provide alternatives where there is more than one strong choice.

Output format:
- Rewritten microcopy
- Alternative options
- Notes on why the changes help

Missing information policy:
Proceed with assumptions unless the context or user goal is unclear.

Quality bar:
- Clear first.
- Short where possible.
- Respect product constraints.
02

Write Better Empty State Copy

Write empty state copy that explains the state, reduces confusion, and nudges the right next action.

You’ll needscreen contextwhy the state occursdesired next actiontoneconstraints
Prompt
You are a UX writer creating empty state copy.

Write the copy for the empty state below.

Context:
- Screen or feature context: [context]
- Why the empty state occurs: [why]
- Desired next action: [action]
- Tone constraints: [tone]
- Constraints or edge cases: [constraints]

Instructions:
1. Clarify what the user is seeing and why.
2. Reduce uncertainty or dead-end feeling.
3. Encourage the most useful next action.
4. Keep the tone aligned with the product.
5. Provide a few options with different levels of warmth or directness.

Output format:
- Option 1
- Option 2
- Option 3
- Recommended CTA text

Missing information policy:
Proceed with assumptions unless the screen context or desired action is unclear.

Quality bar:
- Clear and calm.
- Actionable.
- No decorative filler.
03

Rewrite Error Messages for Better Recovery

Rewrite error messages so users understand what happened, what to do next, and what not to worry about.

You’ll needcurrent error messagescontextlikely causesrecovery actionstone constraints
Prompt
You are a UX writer improving error-state communication.

Rewrite the error messages below.

Context:
- Current error messages: [messages]
- Product or flow context: [context]
- Likely causes: [causes]
- Recovery actions available: [recovery]
- Tone constraints: [tone]

Instructions:
1. Make each message clearer about what happened when possible.
2. Help the user recover without adding unnecessary blame or anxiety.
3. Distinguish actionable errors from purely informational ones.
4. Keep the wording concise and product-appropriate.
5. Flag if an error likely needs UX or product changes beyond copy.

Output format:
- Rewritten messages
- Suggested recovery text
- Notes on product or UX issues behind the copy

Missing information policy:
Proceed with assumptions unless the product context is unclear.

Quality bar:
- Recovery-focused.
- Calm tone.
- Specific where possible.
04

Write UX Guardrail Copy for an AI Workflow Assistant

Write UX guardrail copy for an AI workflow assistant with boundaries, review cues, and trust-setting language.

You’ll needassistant behavioruser contextrisk areastonesurfaces where copy appearsrequired cautions
Prompt
You are writing UX guardrail copy for an AI workflow assistant.

Use the context below.

Context:
- Assistant behavior or capability: [behavior]
- User context: [users]
- Risk areas or likely mistakes: [risks]
- Tone guidance: [tone]
- Product surfaces where the copy will appear: [surfaces]
- Required cautions or review expectations: [cautions]

Instructions:
1. Explain the assistant's boundaries clearly without sounding robotic or alarming.
2. Help users understand when to trust the output and when to review carefully.
3. Write copy that supports safe use and realistic expectations.
4. Adapt the tone to the product context and user sophistication.
5. Keep the copy concise enough for UI surfaces.

Output format:
- Primary guardrail copy
- Shorter alternate microcopy
- Review or caution messages
- Notes on where each variant fits best

Missing information policy:
Proceed with assumptions unless the assistant behavior or risk areas are unclear.

Quality bar:
- Clear boundaries.
- Trust-setting tone.
- Good UI brevity.
05

Write UI Copy That Explains AI State, Confidence, and Review Needs

Write UI copy that explains AI state, confidence, and review needs across key product surfaces.

You’ll needAI workflow behaviorUI surfacesrisk areasuser sophisticationtonerequired cautions
Prompt
You are writing UI copy that explains AI state, confidence, and review needs.

Use the context below.

Context:
- AI workflow behavior or state model: [behavior]
- UI surfaces where this appears: [surfaces]
- Risk areas or likely user confusion: [risks]
- User sophistication or context: [users]
- Tone guidance: [tone]
- Required cautions or review expectations: [cautions]

Instructions:
1. Explain what the system is doing in language users can understand quickly.
2. Clarify what confidence or uncertainty signals mean.
3. Help users know when to trust, review, or intervene.
4. Keep the copy concise enough for UI use.
5. Avoid both false reassurance and unnecessary alarm.

Output format:
- Primary UI copy
- Shorter alternate microcopy
- Confidence or review-state messages
- Notes on best placement

Missing information policy:
Proceed with assumptions unless the AI behavior or UI surfaces are unclear.

Quality bar:
- Clear state explanation.
- Good trust calibration.
- Strong UI brevity.
06

Design the UI Flow for Reviewing AI-Generated Work

Design the UI flow for reviewing AI-generated work, including states, review cues, and user decisions.

You’ll needAI-generated output typeuser rolereview risksapproval or edit needstrust concernsproduct constraints
Prompt
You are designing the UI flow for reviewing AI-generated work.

Use the context below.

Context:
- Type of AI-generated output: [output type]
- User role or reviewer: [user]
- Review risks or likely failure types: [risks]
- Approval, edit, or rejection needs: [review needs]
- Trust concerns: [trust concerns]
- Product constraints: [constraints]

Instructions:
1. Define the flow users should follow when reviewing AI-generated work.
2. Clarify what states, cues, and affordances support good review behavior.
3. Distinguish fast approval cases from high-risk review cases.
4. Surface where users need more context, confidence signals, or edit support.
5. Keep the output concrete enough for UX and product work.

Output format:
- Review-flow overview
- Key screens or states
- User decisions and actions
- Trust and review cues
- Risks or UX pitfalls

Missing information policy:
Proceed with assumptions unless the output type or review needs are unclear.

Quality bar:
- Clear review behavior support.
- Good trust cues.
- Product-design usefulness.