debugging▌

Capture a full DevTools-protocol trace of any browser automation for debugging and analysis.

Structured debugging methodology that mandates root cause investigation before attempting any fixes. \n \n Four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation with mandatory test cases \n Requires completing Phase 1 (evidence gathering, error analysis, data flow tracing) before proposing any fixes; blocks symptom-based patching \n Includes diagnostic instrumentation guidance for multi-component systems and backward call-stack tracing techniques

Tests in real browsers using Chrome DevTools MCP for debugging and inspecting web applications.

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).

If "Index is stale" → run npx gitnexus analyze in terminal.

Accessibility Tree vs DOM: Visually hiding an element (e.g., CSS opacity: 0) behaves differently for screen readers than display: none or aria-hidden="true". The take_snapshot tool returns the accessibility tree of the page, which represents what assistive technologies "see", making it the most reliable source of truth for semantic structure.

SwiftUI debugging falls into three categories, each with a different diagnostic approach:

Systematic bug isolation and root cause analysis through hypothesis-driven debugging methodology. \n \n Applies five-step workflow: reproduce, isolate, hypothesize and test, fix, and prevent through regression tests \n Includes language-specific debugger guidance (Python pdb, Node.js Inspector, Go delve) and advanced strategies like git bisect for regression hunting \n Enforces strict constraints: reproduce first, test one hypothesis at a time, document findings, and remove debug code before com

Guides systematic root-cause debugging for tests, builds, and unexpected errors.

A collection of systematic debugging methodologies that ensure thorough investigation before attempting fixes.