Write Error Messages That Help Users Recover

A user hits an error and the message just says something failed, with no way forward. This writes user-facing messages for your error codes: what happened, why if they can affect it, and the one or two steps to fix it. Under 40 words each, and it never blames the person reading it. Hand over the code list.

You are tasked with writing user-facing error messages for {PRODUCT_NAME}. Here is a list of error codes and their technical causes: {ERROR_CODE_LIST}.

For each error, write a message that follows this formula: what happened (one short sentence), why it happened if the user can influence it (one sentence, optional), and what to do next (one or two actionable steps). Keep each message under 40 words. Never blame the user. Never show raw error codes to the user in the message body: put the code in a collapsible 'Details' block.

Also flag any errors in the list that could be prevented by better UX design and briefly note the design fix, so the team can reduce error frequency at the source.