fidelity
Skill9 starsChanged 2 months agoMITView on GitHub
Spec vs implementation fidelity — Figma/Dev Mode/screenshot compare, spacing tolerance, token remap, close-enough rules. Use when matching a design file, "pixel perfect", "mirip Figma", design QA, or /design with a provided mock.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Kshitijpalsinghtomar/depth-skillstheir own version, first seen Oct 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Kshitijpalsinghtomar/depth-skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/design-system-enforcer.mdcCursor rule
- frontend-expertSkill
- accessibilitySkill
- anti-slop-codeSkill
- anti-slop-designSkill
- app-shellSkill
- architectureSkill
- componentsSkill
- content-designSkill
- data-fetchingSkill
- design-colorSkill
- design-directionSkill
- design-foundationsSkill
- design-surfacesSkill
- design-typographySkill
- design-vocabularySkill
- devtoolsSkill
- engineering-vocabularySkill
- formsSkill
- frontend-expertSkill
- marketingSkill
- monitoringSkill
- motion-inspectionSkill
- motionSkill
- performanceSkill
- polishSkill
- prototypeSkill
- quality-loopSkill
- responsiveSkill
- seoSkill
- skill-authoringSkill
- testingSkill
- tokensSkill
- webglSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
When a design source exists (Figma, screenshot, Spec), compare build to source and close gaps — without inventing a parallel visual system.
- Very specific: line 24
No design source (blank-canvas → design-direction only)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Design Fidelity
Overview
When a design source exists (Figma, screenshot, Spec), compare build to source and close gaps — without inventing a parallel visual system. Prefer project tokens over copying raw hex from the file.
When to use
- User provides Figma / mock / screenshot and wants implementation match
- Design QA / “pixel perfect” / “mirip desain”
/designaudit when a reference image or file is available- Remapping Dev Mode values onto the project token scale
When to skip
- No design source (blank-canvas →
design-directiononly) - Pure copy/token tweak with no layout compare
- User waived fidelity (“approximate is fine”)
Workflow
- Source — note file/frame/screenshot; capture key frames at target breakpoints
- Structure first — layout model, hierarchy, type ladder, Auto Layout Fill/Hug (
responsive) before pixel nits - Token remap — map Figma fills/strokes/radii/type to project tokens (or scored preset). Do not paste foreign hex into production CSS unless the project has no system and the tree allows it
- Compare — spacing, type size/weight, radius, alignment, states (hover/focus if specified)
- Tolerance — see checklist; flag only meaningful deltas
- Report — Before/After or Spec vs Build table; mark remaining intentional differences
Close-enough rules (do not bikeshed)
| Property | Usually OK | Fix |
| Spacing | ±4px on dense chrome | >8px section rhythm drift |
| Type size | Nearest token step | Wrong weight / wrong role (title vs body) |
| Radius | Nearest token | Mixing 3+ one-off radii |
| Color | Token semantic match | Off-token brand / purple slop |
| Alignment | Optical nudge | Broken grid / uneven columns |
Never claim “100% pixel perfect” without side-by-side evidence.
Checklist
- Design source identified (link / frame / screenshot)
- Hierarchy + Auto Layout sizing mapped before polish
- Colors/type/radius remapped to tokens (or explicit waiver)
- Primary breakpoints compared (at least phone + desktop when layout differs)
- States covered if in spec (default / hover / disabled / error)
- Remaining deltas listed (intentional vs TODO)
Depth
Full compare workflow: references/fidelity.md.
Layout map: references/responsive.md (Auto Layout ↔ CSS).
Audit persona: design-reviewer.
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.