Debugging Prompt — the Investigation Contract
"Fix this error" gets guesses. The investigation contract gets a ten-stage diagnosis: facts separated from assumptions, alternatives weighed, fixes justified.
View Resource →Debugging Prompt Generator resources
Build debugging prompts from symptoms, environment, and reproduction steps — root cause first, fix second.
Error Analysis Prompt
An exception is a symptom, not a diagnosis: trace from the throw site back to the root trigger, with the runtime checklist on the table.
View Resource →Debug Performance Problems
Measure before reasoning: find WHERE the time goes, separate latency from memory from throughput, and think at production scale.
View Resource →Debug a Production Incident
Stabilize, then diagnose: impact first, rollback options before intervention, timeline from the deploy history — forensic discipline under fire.
View Resource →Debugging with AI — Done Right
AI is a strong debugging partner and a confident wrong one: the fast-investigation contract that keeps its speed and removes its overconfidence.
View Resource →Investigate Intermittent Bugs
It fails once in twenty runs: the occurrence pattern IS the evidence. Hunt the difference between failing and passing runs — forensically.
View Resource →Investigate Runtime Errors
The error only happens for some inputs: find the implicit contract those inputs violate, with the runtime checklist as the suspect list.
View Resource →Reproduce Software Bugs — Bug Report to Reliable Repro
Support says it happens; nobody can make it happen. Turn a vague bug report — symptoms, environment, expected vs actual — into a reproduction strategy.
View Resource →Root Cause Analysis Prompt
Forensic-grade RCA: most likely cause plus alternatives, each with supporting AND contradicting evidence — and unknowns that stay unknown.
View Resource →Stack Trace Analysis Prompt
Read the trace bottom-up, find the frame where the bad value entered, and name what made it bad — the trace is a map, not an answer.
View Resource →