TechnicalCollectible prompt
Rewrite error messages so users know what to do
Act as a UX writer. Rewrite these error messages for {{product_and_users}}:
{{error_messages}}
For each message:
- Say what happened in plain words, and what the person can do next
- No blame, no jargon, and no raw error codes in the main text; put a code on a secondary line for support if needed
- Aim for 25 words or fewer
- Don't reveal security details, such as whether an email address has an account
Write the final versions in {{output_language}}, using phrasing that sounds natural there rather than a literal translation.
Return a table with columns: original message, rewritten message, button or action label, and notes for developers, such as variables the message needs. Flag any case where the product behavior should be fixed instead of the wording.
Technicalnvoka.com/library/nvoka-rewrite-error-messagesScan to open
Technical
Rewrite error messages so users know what to do
Turn confusing error text into short, helpful messages users can act on.
Curated by Nvoka
ClaudeChatGPTGemini
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 3 filledYour prompt
Act as a UX writer. Rewrite these error messages for {{product_and_users}}:
{{error_messages}}
For each message:
- Say what happened in plain words, and what the person can do next
- No blame, no jargon, and no raw error codes in the main text; put a code on a secondary line for support if needed
- Aim for 25 words or fewer
- Don't reveal security details, such as whether an email address has an account
Write the final versions in {{output_language}}, using phrasing that sounds natural there rather than a literal translation.
Return a table with columns: original message, rewritten message, button or action label, and notes for developers, such as variables the message needs. Flag any case where the product behavior should be fixed instead of the wording.
