Filtar2000

Match Reference — Development skill for Claude Code

Development community

Rebuild a frontend pixel-identical to a reference image.

How to install Match Reference

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Filtar2000/match-reference and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Match Reference does

Rebuild a frontend pixel-identical to a reference image. Coding-agent skill (Claude Code, Codex, Cursor) that measures the gap and returns an actionable per-region fix list — category, perceptual colour delta, the DOM element + CSS, and a fix hypothesis — with image strips, SSIM, and a convergence verdict.

Alternatives in Development

  • Not Claude Code Emulator — ULTRA DANGEROUS CLAUDE CODE EMULATOR; MAKING THE API REQUEST IDENTICAL TO CLAUDE CODE 398 ★
  • Nexus Redeploy — Rebuild frontend and restart Nexus service 131 ★
  • Tech Debt — Multi-agent technical-debt assessment — fans out region-scoped + specialist hunters, verifies findings, scores 107 ★

README

match-reference

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) ![Node ≥ 18](https://img.shields.io/badge/node-%E2%89%A518-3c873a.svg) ![Claude Code · Codex · Cursor](https://img.shields.io/badge/agents-Claude%20Code%20%C2%B7%20Codex%20%C2%B7%20Cursor-6b5bd6.svg) ![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)

A coding-agent skill — for [Claude Code](https://claude.com/claude-code), [Codex](https://openai.com/codex/), Cursor, or any tool that reads `AGENTS.md` — plus standalone Node scripts, that rebuilds a frontend to look **(near) pixel-identical** to a visual reference: a design mockup, a screenshot of another site or app, a photo of a UI, or an existing page you want to clone.

Most visual tools stop at *"here's a red overlay, good luck."* This one **measures the gap and hands the agent a fix list it can execute** — for each wrong zone: what kind of mistake it is, how far off the colour is and in which direction, the exact element and CSS behind it, and a plain-language hypothesis of the cause — then iterates until it converges.

![match-reference loop in action](docs/example/walkthrough.gif)

What makes it different

Free OSS diff tools Paid "Visual AI" (Applitools, Percy…) match-reference
Runs locally, no SaaS ✅ ❌ ✅
Perceptual colour (ΔE), not raw pixels ⚠️ some ✅ ✅
Output an agent can act on (per-element fix list) ❌ ⚠️ (regression-focused) ✅
Rebuild from a foreign mockup/screenshot/photo ❌ (needs your own baseline) ❌ ✅
Convergence verdict across iterations ❌ ⚠️ ✅

The empty quadrant — *local + perceptual + made for an LLM to rebuild-until-identical from an arbitrary image* — is exactly where this sits.

Example

The reference vs. an in-progress build with three mistakes — a lighter button blue, a greyed-out condition label, and tighter card padding:

| Reference | Your build | Diff (`3.72%`) | |---|