browser-visual-qa
Skill1 starsChanged 26 days agoMITView on GitHub
Detect browser automation capabilities, capture screenshots at defined viewport sizes (mobile, tablet, desktop), inspect console errors and network failures, and validate real rendered frontend interfaces.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mowtwo/m2-site-playbooktheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mowtwo/m2-site-playbook★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill to render the implemented interface in a real browser, capture standardized screenshots, monitor console logs, and verify …
- Distinctive: line 15
Runtime Health: Check for JavaScript console errors and failed network assets (missing images, 404 fonts).
- Distinctive: line 16
Empirical Truth: Never report that a page rendered properly without observing actual screenshots or console outputs.
- Distinctive: line 24
Native Agent Browser Tools: If your agent platform provides built-in browser tools (e.g., Antigravity browser tools), invoke them directly …
- Very specific: line 25
Playwright Workflow: If Playwright is installed, use the included capture runner capture.js:
- Distinctive: line 30
Fallback: If neither tool is installed, request developer capture or provide installation instructions:
- Very specific: line 42
Ensure zero uncaught runtime errors (TypeError, ReferenceError).
- Very specific: line 43
Ensure no hydration mismatch warnings in React/Next.js (Warning: Text content did not match).
- Distinctive: line 44
Ensure zero 404 or blocked network requests for fonts, icons, or images.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Browser Visual QA Skill
Use this skill to render the implemented interface in a real browser, capture standardized screenshots, monitor console logs, and verify runtime visual integrity.
Core Responsibilities
- Automation Detection: Detect available browser automation tools (native agent tools vs. Playwright CLI).
- Standardized Viewports: Capture screenshots conforming to Viewport Standards (mobile: 390x844, tablet: 768x1024, desktop: 1280x800).
- Runtime Health: Check for JavaScript console errors and failed network assets (missing images, 404 fonts).
- Empirical Truth: Never report that a page rendered properly without observing actual screenshots or console outputs.
Step-by-Step Procedure
1. Check Available Browser Automation
Inspect available capabilities:
- Native Agent Browser Tools: If your agent platform provides built-in browser tools (e.g., Antigravity browser tools), invoke them directly to navigate and capture screenshots.
- Playwright Workflow: If Playwright is installed, use the included capture runner capture.js:
node skills/browser-visual-qa/scripts/capture.js http://localhost:3000 ./output/rendered-desktop.png --preset desktop node skills/browser-visual-qa/scripts/capture.js http://localhost:3000 ./output/rendered-mobile.png --preset mobile - Fallback: If neither tool is installed, request developer capture or provide installation instructions:
npm install --save-dev playwright && npx playwright install chromium
2. Verify Viewport Dimensions
Confirm that rendered screenshots match the intended dimensions using ves-dimension:
node bin/ves-dimension.js ./output/rendered-desktop.png3. Review Console and Network Health
- Ensure zero uncaught runtime errors (
TypeError,ReferenceError). - Ensure no hydration mismatch warnings in React/Next.js (
Warning: Text content did not match). - Ensure zero 404 or blocked network requests for fonts, icons, or images.
4. Hand Off to Regression Triage
Pass the rendered screenshot and reference mockup to visual-regression-triage for automated pixel comparison.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.