Fidelity
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.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill fidelitygit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/fidelity ~/.claude/skills/fidelityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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” - `/design` audit 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-direction` only) - Pure copy/token tweak with no layout compare - User waived fidelity (“approximate is fine”) ## Workflow 1. **Source** — note file/frame/screenshot; capture key frames at target breakpoints 2. **Structure first** — layout model, hierarchy, type ladder, Auto Layout Fill/Hug (`responsive`) before pixel nits 3. **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 4. **Compare** — spacing, type size/weight, radius, alignment, states (hover/focus if specified) 5. **Tolerance** — see checklist; flag only meaningful deltas 6. **Report** — Before/After or Spec vs Build table; mark remaining intentional differences ## Close-enough rules (do not bikeshed) | Property | Usually OK | Fix | |----------|------------|-----|
Details
- Skill name
fidelity- Repository
- sukirman1901/frontend-expert
- Path
skills/fidelity/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Fidelity skill do?
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.
How do I install the Fidelity skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fidelity popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Forms
9sukirman1901/frontend-expert
Accessible forms, field/form errors, submit pending, wizards, progressive disclosure. Use when building or fixing forms, login, settings, checkout, filters, "validasi", "form error", or multi-step flows.
Engineering Vocabulary
9sukirman1901/frontend-expert
Name a frontend engineering concept from a loose description. Reverse-lookup for FE technical terms — user describes a pattern informally ("supaya gak fetch ulang", "render cuma yang keliatan"), skill returns the proper name + brief definition. Use when the user uses informal language for a technical concept, or when you need the correct term to pick the right implementation.
Frontend Expert
9sukirman1901/frontend-expert
Chat-first frontend UI quality suite — 33 skills across UI Quality, Responsive, Ship FE, and Depth pillars. Token decision tree, compliance gates, anti-AI-slop, motion vocabulary (12 families), marketing landing recipes, and quality loop. Auto-loads on any UI/build/audit/polish request — no slash commands needed.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.