rcode-browser-verify

Verify live browser behavior and UI state using Chrome DevTools MCP.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-browser-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-browser-verify
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/4-implementation/rcode-browser-verify
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-browser-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false confidence from build output alone by checking how a web app actually behaves in a live browser, where DOM state, console errors, network activity, and rendering details can differ from static results.

Core Features & Use Cases

  • Browser Runtime Inspection: Inspect DOM nodes, computed styles, screenshots, console output, and network requests directly in Chrome.
  • Dynamic Verification: Reproduce interactions and compare before-and-after states to catch regressions in real user flows.
  • Performance and Debugging: Trace frame timing, paint behavior, and resource loading issues for animated UIs, Three.js scenes, scroll-driven interfaces, and production-only failures.

Quick Start

Ask the Skill to verify a specific page or component in Chrome using DevTools MCP and report concrete browser evidence for any errors, visual mismatches, or performance issues.

Frequently Asked Questions about rcode-browser-verify

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

FAQPage Schema
How do I verify browser behavior with Chrome DevTools after a build succeeds?

Verify browser behavior by inspecting live DOM state, console errors, and network activity directly in Chrome DevTools, ensuring real runtime evidence confirms UI stability beyond static build output.

What is dynamic DOM inspection and when do I need it for web testing?

Dynamic DOM inspection checks live DOM nodes and computed styles during user interactions. It is needed when static results differ from actual browser rendering, causing visual mismatches or regressions in interactive flows.

How do I trace network requests and console errors in a live browser?

Trace network requests and console errors by capturing real runtime evidence from Chrome DevTools, including request URLs and console logs, to diagnose production-only bugs and resource loading failures accurately.

Can I profile performance and frame timing for Three.js scenes using DevTools?

Profile performance for Three.js scenes by tracing frame timing, paint behavior, and resource loading issues within Chrome DevTools to identify rendering bottlenecks in animated UIs and complex visual interfaces.

What is the best way to catch production-only UI bugs that do not appear locally?

Catch production-only bugs by reproducing interactive flows in a live browser and comparing before-and-after states using screenshots and DOM inspection to gather concrete evidence of the failure.

Why does my web app look different in the browser than the build output suggests?

Browser rendering differs from build output because live DOM state, computed styles, and network activity dynamically alter the UI. Inspect actual browser behavior using DevTools to identify the exact visual mismatch.