Kaboom-Browser-AI-Devtools-MCP

Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot", "browser errors", "network requests", "automate the browser", "record a test", "accessibility audit", "performance check", "what's on the page".

Use when the user wants a full Kaboom quality audit of a web app or tracked site, with one polished report covering Functionality, UX Polish, Accessibility, Performance, Release Risk, and SEO.

Use when user says "QA my app", "find all bugs", "check my app for problems", "debug my whole app", "what's broken", or wants a comprehensive quality review of their web application.

Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift.

Use when user asks to automate browser actions, click buttons, fill forms, navigate pages, run a sequence of browser steps, or build a repeatable workflow.

Use when MCP tools fail to connect, user reports "extension not connected", tool calls return errors, or user asks to check their Kaboom setup.

Use when user reports a bug, broken feature, console error, failed network request, or unexpected page behavior that needs investigation.

Use when user reports a broken page, unexpected behavior, or error and needs fast root-cause identification across multiple signal sources.

Use when user asks to build a product demo, create a walkthrough, record a feature showcase, or produce a repeatable demo script.

Use when user reports slow page load, asks about Core Web Vitals, wants before/after performance comparison, or needs to profile a specific interaction.

Use when user has fixed a bug and needs a test that proves it stays fixed, or when a failure needs to be captured as a reproducible test case.

Use when user asks if a release is ready to ship, needs a go/no-go decision, or wants to run quality gates before deploying.

Use when user asks to stress-test the system, validate reconnection behavior, check for race conditions, or verify end-to-end data flow integrity.

Use when user asks to check for leaked secrets, exposed tokens, or sensitive data in logs, error output, diagnostics, or debug responses.

Use when user asks to audit a website, review all pages, check for broken links, capture full site state, or do a comprehensive product review.

Use when user asks to improve test coverage, find untested code paths, identify risky files without tests, or add missing test cases.

Use when user asks to review UX quality, check accessibility compliance, audit visual hierarchy, or evaluate information architecture on a page.

Use when a tool call fails with "extension not connected", the daemon is unreachable, or browser telemetry stops arriving.