mockup-parity-loop
Skill0 starsChanged 4 months agoNo licenceView on GitHub
The iteration discipline for building a UI screen against a designer-supplied mockup + normative spec. Runs one "measurement round" — capture the build, sample the mockup at the same anchors, compare against the spec's declared values, and report NUMBERS not prose. Enforces the rules that broke the 15-round loop on the Guandan main-menu overhaul into single-digit rounds: replace "visually confirmed" with a sampled pixel or a computed offset every time; distinguish measurable pass ("11px vs spec 15, off by 4") from chirality ("edges at Δy = -30, spec expected +30 → mirrored"); include a chirality check on every rotated element so a mirrored build doesn't pass symmetric measurements. Use whenever the user hands you a mockup image + a spec document and says "match this pixel-for-pixel", "iterate against the mockup", "audit this build against the design", "run the next round", or when a UI PR has visual acceptance criteria and you're about to eyeball it.
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- address-reviewSkill
- coding-principlesSkill
- dev-loopSkill
- dispatchSkill
- harden-permissionsSkill
- mermaid-checkSkill
- mppm-resetSkill
- netcode-checkSkill
- pr-descriptionSkill
- pr-reviewSkill
- pr-screenshotSkill
- pr-sweepSkill
- pr-videoSkill
- run-playmodeSkill
- scene-wireSkill
- ship-issueSkill
- start-taskSkill
- unity-buildSkill
- unity-e2e-verifySkill
- unity-editor-upSkill
- unity-iterateSkill
- unity-local-multiplayerSkill
- unity-mcp-setupSkill
- unity-new-projectSkill
- unity-smart-mergeSkill
- unity-start-taskSkill
- unity-switch-worktreeSkill
- unity-testSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

