Translate a developer-flavored error into one a normal user can act on (Sonnet 4.6).
Modality
Text
Model
claude-sonnet-4-6
Rewrite this error message for a non-technical end-user. Keep it short.
Original message: {{original}}
What the system was trying to do: {{operation}}
What the user can do next: {{next_step}}
Rules:
- Lead with what the user lost or didn't get, not what the system did.
- Say what to try next in one short sentence — a verb in the imperative.
- Don't apologize, don't use 'oops/uh-oh/whoops'.
- Don't say "an unexpected error occurred".
- 25 words max total.
Return ONE rewrite, no commentary.The '25 words max' is the hard guardrail. Without it the rewrite drifts to 60 words and reads like marketing copy.
Embed
Visitors see the card and can run the prompt on Artinstring with their own account.
<iframe src="https://artinstring.com/embed/error-message-rewrite" width="100%" height="420" loading="lazy" style="border:0;border-radius:16px;" title="Error Message — Rewrite · Artinstring"></iframe>More from Writers' Toolkit
Draft a 'what-to-do-with-this' section for a newsletter, after the news bit (Sonnet 4.6).
in Writers' Toolkit
Translate a half-formed PR comment into one that's direct, kind, and unambiguous (Sonnet 4.6).
in Writers' Toolkit
Generate a tailored design critique checklist for a specific surface (Sonnet 4.6).
in Writers' Toolkit