Debugging difficult problems
Reproduction, minimization, instrumentation, feedback, and proof for bugs that resist quick fixes.
Why this collection exists
Replace plausible patches with an explained cause and durable regression protection.
Prompts
Use these directly when the moment calls for a focused process.
Diagnose before fixing
Reproduce, narrow, and prove a root cause before touching production code.
Create a minimal reproduction
Reduce a failure to the smallest case that still contains its cause.
Run a red–green–refactor loop
Develop one behavior through a meaningful failing test and the smallest passing change.
Verify a bug fix
Prove that a fix addresses the root cause, prevents recurrence, and avoids adjacent regressions.
Investigate a performance regression
Measure the regression, isolate the changed cost, and verify the fix against a baseline.
Skills
Install these when the discipline should remain available across sessions.
Workflows
Follow these when the work spans several distinct stages.