Best PromptsDebugging prompts
Help me fix this type error. The full error, unabridged: """ [PASTE THE ENTIRE ERROR INCLUDING EVERY "Types of property X are incompatible" LINE. THE NESTED PART IS USUALLY THE REAL ERROR.] """ The code: """ [PASTE THE FAILING CODE PLUS THE TYPE AND INTERFACE DEFINITIONS INVOLVED] """ TypeScript version and relevant tsconfig settings:
Fix TypeScript Type Errors
Resolve stubborn type errors by reading what the compiler is really saying, with fixes ranked so escape hatches are the last resort.
Logs, traces, or metric output: """ [PASTE THE RAW LOGS, TRACE SPANS, OR METRIC SERIES. INCLUDE THE PERIOD BEFORE THE PROBLEM STARTED, NOT ONLY THE FAILING WINDOW.] """ Analyze the material above. What users reported and when: [SYMPTOM + TIME, WITH TIMEZONE] System shape: [SERVICES INVOLVED AND WHAT CALLS WHAT] What changed recently: [D
Log and Trace Analysis
Turn a pile of logs, traces, or metrics into a timeline, a ranked set of hypotheses, and the one query that would confirm the top one.
Help me debug this issue. Work as a diagnostician, not a guesser. **Symptom**: [WHAT HAPPENS, INCLUDING EXACT ERROR TEXT] **Expected**: [WHAT SHOULD HAPPEN] **Started when**: [RECENT CHANGES, OR "unknown"] **Environment**: [RUNTIME, VERSIONS, OS] **What I've tried**: [ATTEMPTS SO FAR] Relevant code/logs: """ [PASTE] """ Do this: 1. Res
Systematic Debugging
Debug any failure methodically: reproduce, form ranked hypotheses, and identify the single cheapest test that discriminates between them.
Optimize this slow query. Work from evidence, not pattern-matching. Do not propose any change until you've read the actual plan. The query: """ [PASTE THE SQL] """ Execution plan, run and paste: EXPLAIN (ANALYZE, BUFFERS) for Postgres, EXPLAIN ANALYZE for MySQL: """ [PASTE THE FULL PLAN OUTPUT] """ Schema context: table definitions + e
SQL Query Optimization
Fix a slow query the disciplined way: read the real execution plan, change one thing, re-measure, no index guessing without evidence.
Explain this error and find the real cause. The full error + stack trace (paste everything: truncated traces hide the answer): """ [PASTE THE COMPLETE ERROR OUTPUT] """ Language/runtime + framework: [e.g. "Python 3.12 / Django" / "Node 22 / Next.js"] What I was doing when it happened: [THE ACTION/REQUEST/COMMAND] What changed recently: [
Explain This Error
Decode any error or stack trace: read it in the right direction, separate your code from framework noise, and fix the cause, not the symptom.
Help me make this faster, with discipline. Rule zero: no optimization gets proposed until we've seen a measurement that implicates it. What's slow: [THE SYMPTOM + NUMBERS: "the /reports endpoint takes 8s p95" / "this script takes 40 min on 1M rows"] The target: [WHAT FAST ENOUGH MEANS: "p95 under 1s" / "under 5 min", no target, no finish
Performance Optimization
A measure-first optimization loop: profile under real load, rank by Amdahl math, change one thing, re-measure, no speculative micro-tuning.