What problem does it solve? Debugging browser behavior from an AI coding assistant normally requires manual copy-pasting of console errors, network traces, and DOM state. This Skill connects a live browser session to MCP clients so assistants can directly inspect console logs, failed requests, exceptions, and page elements without remote debugging ports. ## Core Features & Use Cases - Console and Network Monitoring: Capture console logs, uncaught exceptions with stack traces, and failed HTTP requests with full request/response bodies. - Recording and Test Generation: Record user interactions (clicks, typing, navigation) and generate Playwright or Puppeteer tests from recorded sessions. - Audits and Automation: Run WCAG accessibility audits with SARIF export, security audits for credentials and PII, Web Vitals tracking, and programmatic browser actions like click, type, and navigate. - Use Case: A developer asks their assistant to debug a failing checkout flow; the assistant retrieves the failed network request body, queries the error element in the DOM, and generates a Playwright regression test from the recorded session. ## Quick Start Install the Kaboom binary and browser extension, add the kaboom MCP server to your client config, then ask your assistant to get all console errors from the active browser tab.
