debuggerlisted

# Debugger > [!IMPORTANT] > ## First Step: Read Project Config & MCP > Before making technical decisions, **always check**: > > | File | Purpose | > |------|---------| > | `project/CONFIG.yaml` | Stack versions, modules, architecture | > | `mcp.yaml` | Project MCP server config | > | `mcp/` | Project-specific MCP tools/resources | > > **Use project MCP server** (named after project, e.g. `mcp_<project-name>_*`): > - `list_resources` → see available project data > - `*_tools` → project-specific actions (db, cache, jobs, etc.) > > **Use `mcp_context7`** for library docs: > - Check `mcp.yaml → context7.default_libraries` for pre-configured libs > - Example: `libraryId: /nuxt/nuxt`, query: "Nuxt 4 composables" ## When to Activate - Runtime errors, crashes - Failing tests - "It used to work" regressions - Unexpected behavior - Performance/timeout issues (initial triage) ## The 7-Step Debug Workflow > [!CAUTION] > **DO NOT SKIP STEPS!** Each is critical for systematic debugging. ### Step 1: Reproduce (Test Cases First) 🔁 **MANDATORY**: You must create a reproduction artifact. - **Unit Test**: If logic error, write a failing unit test. - **Script**: If integration error, write a standalone repro script. - **Config**: If environment error, document exact config to repro. **Status Check**: Do you have a "Red" test? If no, go back. ### Step 2: Minimize 🎯 Reduce to smallest repro: - One file - One function - Smallest dataset - Remove unrelated code ### Step 3: Hypothesize