
Web Debug
Debug web apps systematically with Chrome DevTools and Playwright MCPs
What You Can Do
You can efficiently diagnose and resolve web application issues by combining Chrome DevTools MCP for live browser inspection with Playwright MCP for automated testing and fresh browser instances. The skill automates context discovery from project documentation, validates prerequisites before executing slow operations, and guides you through decision trees for selecting the right debugging approach—whether you're troubleshooting page rendering, network requests, authentication flows, or UI behavior.
Features
Automatically choose between Chrome DevTools MCP (for live sessions) and Playwright MCP (for fresh instances) based on your debugging scenario
Capture and analyze HTTP requests, responses, and status codes to identify API failures and performance bottlenecks
Systematically extract and categorize console messages, errors, and warnings to pinpoint client-side issues
Inspect localStorage, sessionStorage, and cookies to diagnose authentication flow failures
Capture rendered page state, DOM structure, and visual layout to detect rendering and CSS issues
Extract debugging hints from project documentation, README files, and configuration to accelerate diagnosis
Verify prerequisites (port availability, URL accessibility) before executing expensive browser operations
Leverage Playwright's cross-browser support (Chrome, Firefox, Safari, Brave) for compatibility debugging
Example Output
Example 1: Authentication Flow Debugging
Issue: Login fails silently
✓ Validated auth endpoint accessibility
✓ Inspected request headers and response status (401)
✓ Extracted auth token from localStorage
✓ Found missing CSRF token in request body
Resolution: Token validation failed—frontend not including CSRF header
Example 2: API Integration Issue
Issue: Data not displaying on dashboard
✓ Confirmed page loads (200 OK)
✓ Network analysis: GET /api/data returns 500 error
✓ Console shows: "TypeError: Cannot read property 'items' of null"
✓ Backend error log revealed: database connection timeout
Resolution: Backend service down—retry mechanism needed
Example 3: UI Rendering Problem
Issue: Button appears off-screen on mobile
✓ Browser snapshot from Playwright (mobile viewport)
✓ Inspected computed CSS: overflow hidden on parent
✓ Found hardcoded width causing layout break
Resolution: CSS media query needed for responsive design
What's Included
- SKILL.md: Core skill definition with decision trees for tool selection and debugging workflows
- MCP Tool Integration Guide: Instructions for configuring Chrome DevTools MCP (remote debugging setup) and Playwright MCP
- Debugging Decision Trees: Flowcharts for page loading, authentication, API, and UI issues with step-by-step validation sequences
- Context Discovery Framework: Automated documentation parsing to extract auth methods, API endpoints, and configuration from project files
- Network/Console/Storage Inspection Templates: Ready-to-use queries for filtering requests, extracting errors, and analyzing browser storage
Who It's For
- Full-stack engineers debugging web application issues across frontend and backend integration points
- QA/Test engineers performing automated browser testing and cross-browser compatibility validation
- Frontend developers diagnosing UI rendering, CSS, and JavaScript errors in complex applications
- DevOps/SRE teams troubleshooting production web application failures and performance issues
- Security engineers analyzing authentication flows, session management, and API security vulnerabilities
Best For
- Diagnosing blank/broken page loads and rendering failures
- Debugging authentication and session management issues
- Analyzing API integration failures and network request problems
- Identifying JavaScript errors and console-based application crashes
- Testing cross-browser compatibility and responsive design issues
- Inspecting browser storage (cookies, localStorage, sessionStorage) for state management problems







