What problem does it solve? After building or modifying an HTML/UI artifact, you need proof it actually renders correctly — no console errors, expected elements present, responsive breakpoints working — especially when no vision model is available to read screenshots, or when web extraction tools like Firecrawl are unconfigured. ## Core Features & Use Cases - DOM-based verification: Probe element counts, computed styles (colors, radii, grid columns), and page structure through browser_exec instead of eyeballing screenshots. - Responsive testing via CDP: Use Emulation.setDeviceMetricsOverride to trigger real media queries at specific widths, since setting window.innerWidth does not work. - Content extraction fallback: Read full page text and structure from any URL when web_extract/web_search fail due to missing Firecrawl configuration. - Use Case: You built a single-file HTML dashboard and must confirm it opens, renders a 5-column stats grid on desktop, collapses to 1 column at 390px width, and opens a detail sheet when a table row is clicked — all without a test framework. ## Quick Start Use the browser-verify skill to open my artifact.html in a headless browser, check for console errors, and confirm the responsive layout collapses correctly at mobile width.