trove-visual-parity

trove-visual-parity is a skill for Claude Code from bravew/trove. It costs 73 tokens per session (488 once invoked), scanned A, original, MIT.

A method for checking whether two user interfaces look the same by comparing screenshots. It uses image differences to verify each component against a reference version.

In plain words
What is it for?
Use it when matching a new implementation to an existing interface, migrating shared styles, and verifying components with screenshot tests.
Why use it?
It replaces subjective visual checking with repeatable evidence and helps detect layout, spacing, font, and styling changes during a migration.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the trove-design plugin — 4 skills shipped together

Good fit Use it when matching a new implementation to an existing interface, migrating shared styles, and verifying components with screenshot tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bravew/trove/trove-visual-parity
View source ↗ bravew/trove
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add bravew/trove --skill trove-visual-parity
Clone the repo
git clone --depth 1 https://github.com/bravew/trove

Made for: Claude Code.

Or install trove-design, the plugin that ships this one along with the rest of its 4 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for trove-visual-parity

README.md
[![agentmods](https://agentmods.dev/badge/skills/bravew/trove/trove-visual-parity/github.svg)](https://agentmods.dev/skills/bravew/trove/trove-visual-parity)
Your own site
<a href="https://agentmods.dev/skills/bravew/trove/trove-visual-parity"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-visual-parity/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for trove-visual-parity

Your own site · 80×15
<a href="https://agentmods.dev/skills/bravew/trove/trove-visual-parity"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-visual-parity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 488 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.00488
Opus 5 $0.00036 $0.00244
Sonnet 5 $0.00015 $0.00098
Haiku 4.5 $0.00007 $0.00049

Measured 9d ago against content hash 60a16be0b19a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

trove-visual-parity scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/trove-design/.agents/skills/trove-visual-parity/SKILL.md · 33 lines

What it actually says

Trove · v2026.7.4

Session Init

This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.

trove-visual-parity

Prove two implementations render the same, by image diff — not by eyeballing. The baseline is the spec; the new implementation moves to meet it.

Workflow

  1. Establish the baseline first (blocking). Capture the reference rendering with Playwright toHaveScreenshot(). Generate baselines in CI, not locally — local renders (fonts, DPI) drift from CI and create false diffs.
  2. Migrate shared primitives first. Tokens, base components, and shared styles before the components that compose them.
  3. One component at a time. Migrate, then diff against its baseline. Parallel components go in separate worktrees (trove-worktree).
  4. Verify by diff, within a tuned threshold. Use toHaveScreenshot() with maxDiffPixels / maxDiffPixelRatio / threshold tuned to absorb anti-aliasing and font noise without hiding real regressions. It auto-retries until the page stabilizes. A diff above threshold from a real layout/spacing change is a fail.
  5. One PR per component or small batch.

Run the visual suite in isolation

Tag visual tests (@visual) and run them as a dedicated stage, not inside the normal unit run — they need a consistent rendering environment.

The anti-tampering rule

When a diff exceeds threshold, fix the implementation to match the baseline. Never edit the baseline, mask the diffing region, or loosen maxDiffPixels to make a real regression pass. The baseline is the contract; raising the threshold to hide a regression defeats the whole exercise.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 33 lines · 73 tokens per session scan A 60a16be0b19a

Subscribe to this mod's changes

trove-visual-parity is a skill published in the GitHub repository bravew/trove (10 stars, last pushed 10d ago), licensed MIT. It adds 73 tokens to every session and 488 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

davila7/claude-code-templates · 34 tokens

design-qa

Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to…

XiaomiMiMo/MiMo-Code · 68 tokens

health

Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…

tw93/Waza · 71 tokens

hunt

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…

tw93/Waza · 70 tokens

chrome-cdp

Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…

mattzcarey/shippie · 91 tokens

ui-craft-checks

Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…

Orkas-AI/Orkas · 5 tokens