Make error messages actionable
Developers fix their own mistakes instead of filing issues.
The number it moves
Docs blockers
Count of support questions or issues that the docs should have answered.
What your AI does
Grep for thrown errors and HTTP error responses. Find generic messages like 'invalid request' or 'something went wrong'. Propose messages that name the bad field, the expected value and a docs link, with stable error codes.
Done when
- Errors name the bad field and the expected value
- Errors link to the docs
- Every error has a stable code
The prompt
Paste this into any AI coding tool, or run it in MightyMouse and your AI works on your own project.
Make error messages actionable (Developer tool) Grep for thrown errors and HTTP error responses. Find generic messages like 'invalid request' or 'something went wrong'. Propose messages that name the bad field, the expected value and a docs link, with stable error codes. Done when: - Errors name the bad field and the expected value - Errors link to the docs - Every error has a stable code Read the code first. If it already does this well, change nothing and say so. Otherwise make the smallest change that makes every line above true. Work with what this project already uses. Do not add a paid tool or service unless I ask for one. Playbook: https://getmightymouse.com/playbooks/devtool-make-error-messages-actionable/ - published by MightyMouse. Source: Google API Improvement Proposals, https://google.aip.dev/193
The skill file
Save this as SKILL.md and Claude Code or Cursor can run the playbook any time you ask.
--- name: devtool-make-error-messages-actionable description: Developers fix their own mistakes instead of filing issues. Use on a developer tool project to improve "Docs blockers". --- # Make error messages actionable Grep for thrown errors and HTTP error responses. Find generic messages like 'invalid request' or 'something went wrong'. Propose messages that name the bad field, the expected value and a docs link, with stable error codes. ## Done when - [ ] Errors name the bad field and the expected value - [ ] Errors link to the docs - [ ] Every error has a stable code ## How to run it Read the code first and tick every line that is already true. If all are true, change nothing and say so. Otherwise make the smallest change that makes the rest true, then report each line as done or not done. Work with what this project already uses. Do not add a paid tool or service unless I ask for one. Playbook: https://getmightymouse.com/playbooks/devtool-make-error-messages-actionable/ - published by MightyMouse. Source: Google API Improvement Proposals, https://google.aip.dev/193