visual-verification
Skill0 starsChanged 55 days agoApache-2.0View on GitHub
Automated visual regression check via Playwright — 5 DOM checks × 3 viewports (375/768/1280). Produces pass/fail grid + screenshot paths under .arbiter/evidence/visual/.
- Installs packages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- imMamdouhaboammar/Mimeratheir own version, first seen Nov 8, 2026
- poooi/poitheir own version, first seen Oct 8, 2026
- nahid-sparktales/agent-dispatchertheir own version, first seen Sep 21, 2026
- AkshitIreddy/agent-skillstheir own version, first seen Sep 13, 2026
- SebastianKuehnau/sandbox-demotheir own version, first seen Aug 14, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- poooi/poi★ 1.8ksame name
- nahid-sparktales/agent-dispatcher★ 59same name
- AkshitIreddy/agent-skills★ 1same name
- imMamdouhaboammar/Mimera★ 1same name
- SebastianKuehnau/sandbox-demo★ 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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architect-reviewSkill
- brainstormingSkill
- clean-codeSkill
- close-gold-gapSkill
- codebase-auditSkill
- configureSkill
- context-rot-managementSkill
- epic-decomposeSkill
- gold-auditSkill
- impactSkill
- levelupSkill
- product-acceptanceSkill
- refutationSkill
- senior-surveySkill
- ssot-navigationSkill
- tabletopSkill
- tddSkill
- understand-codeSkill
- verificationSkill
- wave-drainSkill
The file
Files
Visual Verification Skill
Invoke when a UI change needs visual validation before marking a task complete.
Usage
node scripts/visual-verify.mjs --url http://localhost:3000 --task-id 700
# Graceful skip when Playwright not installed:
node scripts/visual-verify.mjs --skip-if-missing --url http://localhost:3000 --task-id 700What it checks (5 checks × 3 viewports = 15 datapoints)
| # | Check | Description |
| 1 | page-title | <title> element present and non-empty |
| 2 | no-layout-overflow | body scroll width ≤ viewport width |
| 3 | primary-cta-visible | At least one <button> or <a> element visible |
| 4 | no-console-error | No console errors on page load |
| 5 | screenshot | Full-page screenshot captured for review |
Viewports: 375px (mobile), 768px (tablet), 1280px (desktop).
Output schema
Results written to .arbiter/evidence/visual/<task-id>/<page>.json:
{
"url": "http://localhost:3000",
"task_id": "700",
"timestamp": "2026-05-17T11:00:00Z",
"viewports": [
{
"width": 375,
"checks": {
"page-title": { "pass": true },
"no-layout-overflow": { "pass": true },
"primary-cta-visible": { "pass": false, "detail": "no visible CTA found" },
"no-console-error": { "pass": true },
"screenshot": { "pass": true, "path": ".arbiter/evidence/visual/700/375.png" }
}
}
],
"summary": { "total": 15, "passed": 14, "failed": 1 }
}When Playwright is absent
With --skip-if-missing, the script exits 0 and writes a skip marker:
{
"skipped": true,
"reason": "Playwright not installed",
"install": "npm install -D @playwright/test && npx playwright install chromium"
}Without --skip-if-missing, it prints install instructions and exits 1.
Prerequisites
npm install -D @playwright/test
npx playwright install chromiumTask completion gate
A task with UI changes is complete only when ALL 15 datapoints pass (or the task explicitly waives specific checks with documented justification in the PR description).
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.

