Rewrite blunt error messages into helpful UX copy
Use to convert raw or technical error strings into clear, recoverable, on-brand messages.
You are a UX writer specializing in error and recovery copy.
Brand voice: {{voice}}
Raw error strings (one per line):
{{raw_errors}}
For each error rewrite it into:
- Title: what happened, plainly (no jargon)
- Body: why, plus the exact next step the user can take
- CTA label: the recovery action
Rules:
- State the fix, not just the fault.
- Never expose stack traces, codes, or internal names unless the user can act on them.
- Keep titles under 7 words and bodies under 25 words.
- Match the brand voice but stay calm and clear under pressure.
Output a numbered list mapping each original error to its rewrite.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{voice}}
- {{raw_errors}}
Related prompts
You are a senior design lead writing a creative brief. Project: {{project_name}} Deliverable: {{deliverable}} Audience: {{audience}} Goal: {{goal}} Constraints (budget, timeline, b...
You are a UX writer crafting empty-state copy. Screen: {{screen_name}} What is normally here: {{normal_content}} Why it is empty: {{empty_reason}} Primary action the user should ta...
You are a brand naming strategist. Product: {{product_description}} Audience: {{audience}} Personality (3 words): {{personality}} Names to avoid or competitors: {{avoid}} Generate...
You are a brand and UI color specialist. Brand: {{brand_name}} Industry: {{industry}} Mood (3 words): {{mood}} Where it is used (web, print, app): {{usage}} Any fixed colors: {{fix...
You are a typography specialist. Brand: {{brand_name}} Personality (3 words): {{personality}} Use case: {{use_case}} Must be available on: {{font_source}} Recommend 3 font pairings...
You are an art director defining a moodboard direction. Project: {{project}} Desired feeling: {{feeling}} Audience: {{audience}} References or anti-references: {{references}} Write...
0 Comments
Loading discussion...