web-render-verify

Verifies web page rendering using Playwright MCP computed styles and viewport checks.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill web-render-verify-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-render-verify
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/web-dev/web-render-verify
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill web-render-verify-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Visual claims about a web build are unverified without actually rendering the page in a real browser. This Skill grounds design verdicts in real computed styles and catches layout bugs that self-review misses, while avoiding two common traps on Windows hosts. ## Core Features & Use Cases - Real Browser Rendering: Serves the project over HTTP and navigates with the Playwright MCP to read computed styles like font-family, background-color, box-shadow, and border-radius. - Responsive Overflow Detection: Resizes to mobile viewport (390x844) and compares scrollWidth against innerWidth to detect horizontal overflow and elements wider than the viewport. - Trap Avoidance: Documents why browser_exec fails on Windows (remote debugging popup) and why file:// URLs are blocked by Playwright, requiring an HTTP server first. - Use Case: After building an HTML landing page, render it at desktop and mobile widths, verify the computed styles match the design intent, and confirm no horizontal overflow before declaring the build done. ## Quick Start Use the web-render-verify skill to serve my project over HTTP and verify it renders correctly at desktop and mobile widths with Playwright.

Frequently Asked Questions about web-render-verify

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

FAQPage Schema
How do I verify a website renders correctly with Playwright?▼

Serve the project over HTTP with python -m http.server, then use the Playwright MCP browser_navigate to load the page and browser_evaluate to read getComputedStyle values. Resize the viewport to check both desktop and mobile rendering.

Playwright MCP vs browser_exec for web rendering verification?▼

Playwright MCP navigates and evaluates pages cleanly with no popups, while browser_exec launches Chrome with remote debugging that triggers an "Allow remote debugging?" dialog on Windows and fails. Reserve browser_exec for multi-step UI automation the MCP cannot do.

Why does Playwright browser_navigate fail with file:// URLs?▼

The Playwright MCP blocks the file: protocol and returns "Access to file: protocol is blocked." Serve the project over HTTP first using python -m http.server, started with background=true so the foreground guard does not refuse it.

How do I detect horizontal overflow on mobile viewports?▼

Resize the browser to 390x844 and compare document.documentElement.scrollWidth against window.innerWidth; overflow exists if scrollWidth exceeds innerWidth by more than 1 pixel. Also scan each element's getBoundingClientRect().right for children wider than the viewport.

Why does browser_exec fail on Windows with a remote debugging error?▼

browser_exec launches Chrome with remote debugging enabled, which pops an "Allow remote debugging?" dialog on Windows hosts. The call fails with a browser-harness remote-debugging-setup error and no render occurs, so use the Playwright MCP instead.