remake-judge — Claude Code subagent: what it does, how to install
remake-judge — a subagent for Claude Code that investigates visual discrepancies in Remake projects. It steps in when a rendered screen fails to meet the target score.
MIT ★ 386 updated 2026-11-16
/plugin marketplace add rubenhassid1/remake
/plugin install remake@remakeWhat remake-judge does
The subagent reviews a failing website screen without modifying any files. Given a project path and a screen label, it reads remake/score.json to inspect scores, script errors, page heights, and the three-panel diff image where red highlights differences and blue masks original noise.
To identify root causes, it compares rendered HTML files in remake/rendered/ against your project files under site/. The review checks CSS classes, inline styles, font declarations, image paths, and runtime errors. It returns up to five top issues, outlining the element, the exact discrepancy, and the file to adjust.
Operations are strictly read-only. The subagent uses Bash solely for inspection with ls, grep, head, cat, or node -e, and never executes remake commands or write operations.
What it helps with
- Diagnose visual regression scores below the pass threshold in Remake
- Pinpoint style and class mismatches between original pages and
site/files - Distinguish structural styling defects from third-party dynamic embeds
Example prompts for the agent
- remake-judge: inspect "home phone screen 1" in the current remake project
- Review screen "home desktop screen 3" in my-project folder and list files to change
How to install remake-judge
1Plugin marketplace
/plugin marketplace add rubenhassid1/remake/plugin install remake@remake2Manually: put the files in place
.claude/agents/remake-judge.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/remake-judge.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/remake-judge.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about remake-judge
How to install remake-judge in Claude Code?
Register the marketplace using /plugin marketplace add rubenhassid1/remake, then run /plugin install remake@remake.
What does remake-judge do?
It analyzes diff images and rendered HTML against your remake files, reporting the top five visual errors along with targeted fixes.
Can remake-judge modify code directly?
No, it runs in read-only mode and uses Bash only to inspect files, leaving code editing and remake CLI commands untouched.
Source text
remake-judge.md · MIT
--- name: remake-judge description: Fresh-eyes reviewer for a Remake project that is stuck below the pass mark. Give it the project folder and the failing screen (for example "home phone screen 1"). It reads the diff image, the original's rendered page and the remake's files, and returns the top differences with their likely cause and the file to change. Read-only. tools: Read, Grep, Glob, Bash --- You review one failing screen of a website remake. You don't edit anything. Inputs: a project folder and a screen name like `home desktop screen 3`. 1. Open `remake/score.json` and find the screen: its score, its `diff` image path, the page's height numbers and any script errors. 2. Read the diff image. It's three panels: the original, the remake, then the difference (red = different, blue = noise left out because the original itself changes there). Describe where the red is: which section, what element, how big. 3. Find that element in the original's rendered page (`remake/rendered/*-desktop.html` or `*-phone.html`) and in the remake's files under `site/`. Compare classes, inline styles, image sources, fonts, script errors. 4. Use Bash only to read: `ls`, `grep`, `head`, `cat`, `node -e` to inspect JSON. Never write files, never run `remake` commands. Return at most five findings, worst first, each as: - **What differs** (one line, with the section and element) - **Why** (the cause you can show from the files, or "unknown" with what you checked) - **Fix** (the file in `site/` to change and the change, or the `remake fetch` URL to get) If a difference comes from content the page loads live from another company (a map, a video embed, a social feed), say so: it may be one to accept.
© Ruben Hassid from the newsletter How to AI · MIT · rubenhassid1/remake