Debugging prompts

---
name: performance-optimization
description: Diagnose and fix performance problems. Use when something is slow, when the user mentions latency, memory, load time, or throughput, or when asked to optimize code.
---

# Performance Optimization

No optimization without measurement. An intuition about what is slow is a hypothesis, and in p
SKILL.md

Performance Skill

A skill that forces measurement before optimization: a baseline, a profile, one change at a time, and the number that proves it worked.

Skilladvanced
---
name: diagnosing-bugs
description: Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
---

# Diagnosing Bugs

A discipline for hard bugs. Skip phases only when explicitly justified.

When exploring the codebase, read `CONTEXT.md`
SKILL.md

Diagnosing Bugs Skill

A six-phase discipline for hard bugs: build a tight, red-capable feedback loop before any hypothesis, then reproduce, minimise, instrument, and fix.

Skillintermediate
---
name: systematic-debugging
description: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
---

# Systematic Debugging

## Overview

**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

**Violating the letter of this process is violating the spirit of
SKILL.md

Systematic Debugging Skill

The Iron Law of debugging as a skill: no fixes without root-cause investigation first, four phases, a red-flags table, and named rationalizations.

Skillintermediate

Search prompts

Find a prompt by title, description, tag, or category.