“debugging”

Use when debugging DuckHTS in webR, duckdb-wasm, or Emscripten/browser workers.

Debugging workflow that MUST reproduce, investigate, fix, and verify unexpected behavior.

Executes JavaScript in browser pages, captures console output, and debugs page-side behavior with cdp.

Diagnoses and fixes runtime bugs in Capacitor iOS/Android apps - white/blank screen on launch, startup crashes, `"X" plugin is not implemented on…

4-phase root cause analysis and debugging

Use for ANY bug, test failure, crash, or unexpected behavior.

Use when diagnosing Flutter layout issues, inspecting widget rebuilds, setting breakpoints, or tracking down UI rendering anomalies.

Use when debugging a failure, test error, exception, or unexpected behavior in the AI Orchestration project, before reading files broadly.

Use when debugging a failure, test error, exception, or unexpected behavior in the AI Orchestration project, before reading files broadly.

Systematic debugging.

Diagnoses and root-causes Amazon MWAA workflow failures across Provisioned (Python DAG) and Serverless (YAML workflow) environments.

Plan, implement, or review systematic debugging work in an existing codebase with compatibility, security, and verification controls.

A systematic approach to debugging complex issues.

Troubleshoot Java backend failures through reproduction, evidence, root cause, and verification.

Find and repair unresolved root causes.

Debug sub-mode for Phase 3 — Investigate → Analyze → Hypothesize → Implement, with the iron rule that no fix ships before root-cause investigation.

Systematic debugging with structured reproduction and root cause analysis.

Disciplined debugging methodology.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts…

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

Debug failures by finding evidence and root cause before changing code.

Debug REST, GraphQL, webhook, and OAuth/API-key integrations with layered request, auth, schema, and response checks.

Debug issues by investigating logs, database state, and git history