Verify visual

Skill jajupmochi/agent-harness/skills/general/verify-visual

Linlin's curated AI agent harness configuration: workflow rules, skills, hooks, plugin recommendations, tooling preferences, and project templates. Loadable into any new project so a fresh /init can pick the relevant subset.

Install

npx -y skills add jajupmochi/agent-harness --skill verify-visual

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use chrome-devtools MCP to screenshot a target URL/element and visually verify it matches a reference. Auto-fires when the user requests a UI change with a visual reference (paired with the ui-iteration-loop rule).

SKILL.md

2.5 KB, as published. Nobody here has run it

/verify-visual

Visually verify a UI change against a reference using chrome-devtools MCP.

Pre-flight

Confirm chrome-devtools MCP plugin is installed and not deprecated (per plugin-preflight rule)
Confirm the dev server is running (use /preview first if not)

Steps

Acknowledge what you're verifying — re-state the change and the reference (1 line).
Navigate to the target page using chrome-devtools MCP (navigate / navigate_page).
Screenshot the relevant element (or full page) via take_screenshot / take_snapshot.
Self-critique against the reference on the 4 axes (per ui-iteration-loop rule):
- Color — palette, contrast, accent
- Typography — font, weight, size, line-height
- Spacing — padding, margin, gap, rhythm
- Ornamentation — borders, shadows, decorative elements
Show user the screenshot + 1-line verdict (match / off / specific axis to retry).

Output format

Verifying <change> against <reference> — 4 axes:
- Color: ✓ matches reference accent
- Typography: ✓ font + weight align
- Spacing: ⚠ slightly tighter than reference (~2 px less rhythm)
- Ornamentation: ✓ no shadow drift

Screenshot: <path-or-url>
Verdict: 80% match. Tighten rhythm next, or ship as-is?

When NOT to use

Micro-edits (single property tweak, copy fix) — skip per output-brevity companion rule
No reference provided — there's nothing to verify against
chrome-devtools MCP unavailable — ask the user how to proceed rather than fall back to blind edits

Lighthouse integration

When the visual concern includes performance / SEO / accessibility (not just look):

chrome-devtools MCP also exposes Lighthouse via lighthouse_audit (Chrome's built-in version)
No npm install of lighthouse needed for ad-hoc audits
For CI / scheduled audits, install @lhci/cli separately (see recommendations/web-auditing.md)

Companion rules

ui-iteration-loop — when running an autonomous 8-iteration loop, this skill is invoked at each iteration's "screenshot + critique" step
plugin-preflight — verify chrome-devtools MCP installed before first invocation in a session
tool-proactivity — fire this skill automatically when the task involves visual verification, with a one-line announcement