Loop/Prompt Library / Code quality & refactoring
🔁 Friendly error messages
Finds every error message a user can see and rewrites the confusing ones in plain words with a clear next step.
Use it when: Users see scary or technical errors like stack traces or codes.
🛑 Stops when: Every user-facing error in scope is rewritten and checked in a real screen, or marked blocked with a reason.
Copy this loop
Find every error message a user can see in [app or part of the app]. Put them in a spreadsheet: where it lives, what triggers it, current text, how bad it is for the user, new text, and whether it was checked. Rewrite the worst ones first, one group at a time, in plain language with a helpful next step. Never show internal names, codes, or stack traces. After each group, run the tests and trigger the error in a real browser if you can. Work through at most [8] groups. Stop when every row is checked or marked blocked. Send me the spreadsheet and proof.
Review every change the agent makes before you keep it. Set a budget or round limit — the prompt includes one.
Idea from Forward Future's Loop Library · by Will Undrell (@WillUndrll). Prompt rewritten in plain English by FixKit AI.
More loops like this
Safe refactor (keep the shape)
Improves one part of the code, one small change at a time, without changing how the rest of the system talks to it.
Refactor until the design feels right
Reshapes a messy codebase step by step, testing and saving a checkpoint after each big step.
Tidy-up pass
Finds small messes like unused code, old comments, and broken links, and cleans them up one safe fix at a time.
Change it everywhere
After you change a value like a version number or a name, it hunts down every old copy so nothing is left out of date.
Branch and worktree cleanup
Sorts through old branches, pull requests, and work-in-progress, rescues anything useful, and removes what is truly dead.
React Doctor: perfect score
Uses the React Doctor tool to push every React app in a project to a real 100 out of 100 health score.