carmack-mode

To fix production bugs with minimal code changes, read the actual source files first to locate the root cause, then apply the smallest surgical edit necessary and run type-checks, linters, builds, and tests to prevent regressions.

Finding the root cause of an urgent performance regression requires inspecting the real source code directly instead of treating symptoms, digging until the true cause is identified, and then making a minimal targeted edit to resolve it.

The best way to resolve a recurring unresolved bug without broad refactors is a surgical workflow that diagnoses the true root cause first and applies only the minimal, safest code edit required to fix the specific issue.

To clean up an uncovered setInterval causing a memory leak in a React application, inspect the source file, add the minimal cleanup logic required, and run type-checks, builds, and targeted tests to ensure no regressions occur.

To remove mock data accidentally shipped to production without breaking existing features, locate the mock data in the source, make a minimal targeted edit to remove it, and verify success by running type-checks, linters, builds, and tests.

To replace a failing third-party fallback with a simple robust check in a TypeScript codebase, read the source to understand the failure, apply the smallest safe edit replacing the fallback, and run type-checks and tests to confirm stability.