After this, the AI surfaces only the refactors that earn their keep — turning shallow modules into deep ones with small, stable interfaces. For developers tired of refactor suggestions that are cosmetic, churn-inducing, or both. Before: "Refactor this module" [Returns 47 suggestions: rename variables, extract functions, add JSDoc, convert to arrow functions. Most are cosmetic. None change the actual brittleness.] After: "Refactor this module" "Three refactors worth doing: 1. Extract URL-building from fetchUser and fetchOrder into one apiPath() helper. Same bug fixed in two places now → one fix in the future. Impact: high. 2. Move retry logic from caller code into a withRetry wrapper. Currently duplicated in 4 callers, each slightly different. Impact: medium. 3. Replace the 14-line config validation with a Zod schema. Catches bugs at boot, not at first use. Impact: medium. The other 30 candidates I considered are cosmetic. Skip them." Use when the codebase feels brittle the user wants an architecture review the same area keeps generating bugs across files Three ways to use this Paste it (any AI, 30 seconds, no install)Open the .md file, copy contents, paste into Claude / ChatGPT / Cursor / Perplexity with: "Read this and apply it whenever the task it describes comes up in our conversation." Done. Install it (Claude Code / Cursor users)Drop the unzipped folder into ~/.claude/skills/ (Claude Code), .cursor/skills/ (Cursor), or your IDE's equivalent. Auto-loads next session. New to AI assistants? Get Claude free at claude.ai, then use Option 1. €7
