طراح پیام خطای کاربرپسند
Why this prompt matters
Error messages are often the most-read text in an app. Actionable messages reduce support tickets by up to 30%.
What we use it for
UX writing
Prompt
Rewrite these error messages to be user-friendly. Each message should: 1) Say what happened in plain language (no jargon), 2) Explain why it happened if known, 3) Tell the user exactly what to do next, 4) Include a way to get help if the fix doesn't work. Keep messages under 30 words for inline errors, under 60 for full-page errors.
Result
**Before**: `Error 403: Forbidden` **After**: "You don't have permission to view this page. If you think this is a mistake, contact your workspace admin or try signing in with a different account."
**Before**: `ETIMEDOUT: connection timed out` **After**: "We couldn't reach the server. Check your internet connection and try again. If this keeps happening, our status page has the latest updates."
**Before**: `Validation failed: field 'email' is required` **After**: "Please enter your email address to continue."
Error messages are often the most-read text in an app. Actionable messages reduce support tickets by up to 30%.
This prompt demonstrates a structured approach to ux writing, producing consistent, high-quality results that can be iterated upon.