browser-testing-with-devtools

Inspect live browser DOM, console logs, and network traffic via Chrome DevTools MCP.

Updated May 27, 2026
One-click install
npx skills add https://github.com/santanapol/agent-skills --skill browser-testing-with-devtools-santanapol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/santanapol/agent-skills/tree/main/.cursor/skills/browser-testing-with-devtools
Command: npx skills add https://github.com/santanapol/agent-skills --skill browser-testing-with-devtools-santanapol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static code analysis cannot detect runtime issues that only appear when a web app runs in a real browser, such as UI layout bugs, uncaught console errors, failed network requests, performance bottlenecks, and accessibility gaps that prevent screen reader users from interacting with the interface.

Core Features & Use Cases

  • Live UI Debugging: Inspect DOM structures, computed styles, and element accessibility to fix layout, styling, and interaction issues.
  • Runtime Error Diagnosis: Analyze console logs to catch uncaught exceptions, framework warnings, and security alerts that only appear during execution.
  • Network & Performance Validation: Monitor API request payloads, response status codes, and performance traces to resolve slow load times and failed data fetches.
  • Accessibility Compliance Checks: Review accessibility trees and tab order to ensure the interface works for users with disabilities.
  • Use Case Example: If a form submission fails silently, use this skill to monitor network requests for the submission call, check the console for hidden errors, and inspect the submit button's DOM state to identify the root cause.

Quick Start

Use the browser-testing-with-devtools skill to inspect the DOM and console logs of the running web app at http://localhost:3000 to debug the button click issue that is not triggering the expected API call.

Frequently Asked Questions about browser-testing-with-devtools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug runtime UI bugs and console errors that only appear in a real browser?

Debug runtime UI bugs and console errors by connecting to a configured Chrome DevTools MCP server to inspect live browser DOM, monitor console logs, and trace network traffic. This catches uncaught exceptions and layout issues undetectable via static code analysis.

What is the best way to monitor API requests and diagnose silent form submission failures?

Monitor API requests by capturing network traffic payloads and response status codes through Chrome DevTools integration. Diagnose silent form submission failures by checking network request failures alongside hidden console errors and the submit button's live DOM state.

How do I check accessibility compliance and tab order in a running web application?

Check accessibility compliance by inspecting the live DOM's computed styles and reviewing the accessibility tree to verify tab order. This ensures the interface works for screen reader users and resolves runtime interaction gaps missed by static analysis.

Do I need a Chrome DevTools MCP server to profile frontend performance metrics?

Yes, you need a configured Chrome DevTools MCP server to access live browser performance trace data. Profiling performance metrics requires this runtime connection to analyze slow load times and resolve frontend bottlenecks undetectable in static code.

Can I use static code analysis to catch network failures and uncaught exceptions?

No, static code analysis cannot detect runtime network failures or uncaught console exceptions. You must use live browser debugging with Chrome DevTools to monitor API request payloads, inspect runtime DOM states, and analyze execution logs for security alerts.

Why does my web app fail to fetch data without showing any static code errors?

Data fetch failures occur at runtime and require live network monitoring to diagnose. Use Chrome DevTools to monitor API response status codes, inspect console logs for hidden framework warnings, and validate the live DOM state to identify the root cause.