debugging▌

Intermittent issues are the most difficult to debug because they don't occur consistently. Systematic approach and comprehensive monitoring are essential.

Use this skill when:

Use when:

This starts both backend (Streamlit/Python) and frontend (Vite/React) with hot-reload. The app URL is printed on startup (default http://localhost:3001; 3000 is reserved for manual make frontend-dev; it may use 3002+ if other debug sessions are running). Avoid pinning VITE_PORT unless you have a specific hard requirement (last resort).

Check dependencies BEFORE blaming code. Core principle 80% of persistent build failures are dependency resolution issues (CocoaPods, SPM, framework conflicts), not code bugs.

Browser debugging tools help identify and fix client-side issues including JavaScript errors, layout problems, and performance issues.

$22

Systematically isolate and fix code issues using structured debugging methodologies. \n \n Covers six-step debugging workflow: information gathering, reproduction, isolation, root cause analysis, fix implementation, and verification \n Includes common bug patterns (off-by-one, null references, race conditions, memory leaks, type mismatches) with targeted solutions \n Provides debugging techniques: binary search isolation, print/log debugging, divide-and-conquer code elimination, and regression t

Systematic debugging framework using competing hypotheses to identify root causes across multiple failure categories. \n \n Generates hypotheses across six failure mode categories: logic errors, data issues, state problems, integration failures, resource issues, and environment mismatches \n Establishes evidence standards with citation requirements (file:line references) and confidence levels (high/medium/low) to avoid confirmation bias \n Supports parallel agent investigation with structured re