browser-runtime-verification

Verify browser UI behavior with runtime evidence and emit a browser-runtime-report.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill browser-runtime-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-runtime-verification
Source: https://github.com/vTRKA/supervibe/tree/main/skills/browser-runtime-verification
Command: npx skills add https://github.com/vTRKA/supervibe --skill browser-runtime-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents false confidence by verifying browser-facing behavior with real runtime evidence instead of relying on compilation output, static screenshots, or unit tests that never hydrate or execute the full UI.

Core Features & Use Cases

  • Runtime evidence capture: Collects console output, page errors, DOM state, network request outcomes, performance signals, and process/cleanup status.
  • Visual + accessibility verification: Records screenshots across required viewports and checks keyboard reachability, focus, accessible names, landmarks/headings, and error announcements.
  • Advanced surface proof: Validates video/media playback and fallbacks, canvas/WebGL health (including no-WebGL behavior), and visual-diff evidence with baseline/current/diff mapping and verdict logic.

Quick Start

Run browser-runtime-verification by telling your AI to verify the target route in a real preview/browser session and produce a browser-runtime-report with screenshots, console/network/DOM evidence, accessibility notes, and a PASS/FAIL/PARTIAL/BLOCKED verdict.

Frequently Asked Questions about browser-runtime-verification

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

FAQPage Schema
How do I verify UI behavior with real browser runtime evidence before shipping?

You can verify UI behavior by running a real preview/browser session that captures console errors, failed network requests, and DOM state to produce a browser-runtime-report. This prevents false confidence from relying solely on compilation output or static screenshots.

What is browser runtime verification for SPA preview routes?

Browser runtime verification for SPA preview routes is the process of validating hydrated UI execution using proof-grade receipts. It collects performance signals, DOM state, and process cleanup status to confirm the application behaves correctly in a real browser environment.

How do I check accessibility and visual regression across required viewports?

Checking accessibility and visual regression involves recording screenshots across viewports and testing keyboard reachability, focus, and accessible names. Visual-diff evidence maps baseline, current, and diff states to produce a clear PASS, FAIL, PARTIAL, or BLOCKED verdict.

Does canvas and WebGL health checking validate fallback behavior when WebGL is unavailable?

Canvas and WebGL health checking validates advanced-surface proof and explicitly includes no-WebGL behavior validation. It ensures your application handles missing graphics contexts gracefully and records the fallback evidence in the final report artifact.

Can I use browser runtime verification for browser-extension surfaces and responsive layouts?

Yes, browser runtime verification applies to browser-extension surfaces, responsive layout changes, and SPA preview routes. It captures runtime evidence and viewport coverage to ensure consistent behavior across different extension environments and screen dimensions.