Loop/Prompt Library / Code quality & refactoring
🔁 Refactor until the design feels right
Reshapes a messy codebase step by step, testing and saving a checkpoint after each big step.
Use it when: The structure of your app is getting in the way and you can describe the better shape you want.
🛑 Stops when: The structure matches the target you described and all checks pass after the last step.
Copy this loop
Refactor [project] toward this target design: [describe the shape you want]. After each meaningful step, run the app for real, ask a second reviewer (or a fresh agent) to check the change, and make a git commit. Keep a running log in [notes file, e.g. /tmp/refactor-notes.md]. Stop when the code matches the target and checks pass, or after [10] steps, whichever comes first. Summarize what moved and what is left.
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 Peter Steinberger. 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.
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.
React Doctor: small-batch fixes
Fixes a handful of real React problems at a time and keeps only the fixes that make the scan better.