design-to-code-check

design-to-code-check is a skill for Claude Code from murphytrueman/design-system-ops. It costs 71 tokens per session (3,346 once invoked), scanned A, original, MIT.

A focused review that compares one design specification with its implemented code for a component or screen. It reports differences and separates coding mistakes from parts of the design that were not specific enough.

In plain words
What is it for?
Use it to check whether a screen or component matches its design, identify visual or behavioural discrepancies, and document missing or ambiguous requirements.
Why use it?
It helps explain whether a mismatch came from incorrect implementation or an unclear design decision. This makes it easier to fix the right source of the problem.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the design-system-ops plugin — 36 skills, 4 commands shipped together

Good fit Use it to check whether a screen or component matches its design, identify visual or behavioural discrepancies, and document missing or ambiguous requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/murphytrueman/design-system-ops/design-to-code-check
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add murphytrueman/design-system-ops --skill design-to-code-check
Clone the repo
git clone --depth 1 https://github.com/murphytrueman/design-system-ops

Made for: Claude Code.

Or install design-system-ops, the plugin that ships this one along with the rest of its 36 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-to-code-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/murphytrueman/design-system-ops/design-to-code-check/github.svg)](https://agentmods.dev/skills/murphytrueman/design-system-ops/design-to-code-check)
Your own site
<a href="https://agentmods.dev/skills/murphytrueman/design-system-ops/design-to-code-check"><img src="https://agentmods.dev/badge/skills/murphytrueman/design-system-ops/design-to-code-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-to-code-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/murphytrueman/design-system-ops/design-to-code-check"><img src="https://agentmods.dev/badge/skills/murphytrueman/design-system-ops/design-to-code-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.03346
Opus 5.5 $0.00028 $0.01338
Sonnet 5.5 $0.00014 $0.00669
Haiku 4.5 $0.00007 $0.00335

Measured 28d ago against content hash 5211373d2222, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-to-code-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 28d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/design-to-code-check/SKILL.md · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design-to-code check

A skill for reviewing the alignment between a design specification and its code implementation, producing a structured discrepancy report catalogued by dimension and severity.

Before you begin: verify references

Confirm that every path in this skill's frontmatter references: exists relative to this SKILL.md. If any is missing, stop: the install is incomplete, usually because a flattening installer (for example npx skills install) dropped the repo-root knowledge-notes/ directory. Tell the user to reinstall by a method in 1-INSTALL.md and run verify-install.sh from the install root. Proceed without the references only if the user explicitly says to, and then say in the output that it was produced without the pack's reference material.

Context

Design-to-code alignment reviews catch two different categories of problem. The first is implementation error — the developer built something different from what was specified, either by mistake or because the specification was unclear. The second is specification ambiguity — the design did not define behaviour completely enough for the developer to implement it correctly, and the developer made a reasonable guess that turned out to be wrong.

Both categories matter, but they require different responses. An implementation error needs to be corrected in the code. A specification ambiguity needs to be corrected in the design and documented, so the same guess does not get made again.

This skill produces a report that distinguishes between the two.


Configuration

If .ds-ops-config.yml exists, follow the configuration-and-recurring knowledge note (../../knowledge-notes/configuration-and-recurring.md) for loading, integration fallbacks and recurring runs. This skill reads:

  • severity.* — discrepancy severity overrides, especially specification_gap and missing_interaction_state
  • system.framework and system.styling — pre-select framework-specific checking guidance
  • integrations.figma — the design specification (see below)
  • integrations.chromatic — visual regression data as a supplementary signal
  • integrations.github — the component source
  • gates.design_to_code — if running as part of component-to-release, determines which findings block release

Read the full file on GitHub · 235 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 28d ago Changed · +1 lines · +12 tokens per session 5211373d2222
  2. 29d ago Changed · -13 lines · -36 tokens per session ba4f6365671f
  3. 1mo ago First seen · 247 lines · 95 tokens per session scan A 57c24c82b8d5

Subscribe to this mod's changes

design-to-code-check is a skill published in the GitHub repository murphytrueman/design-system-ops (210 stars, last pushed 28d ago), licensed MIT. It adds 71 tokens to every session and 3,346 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

fmcp-token-sync-orchestrator

Figma design token'larını kod dosyalarıyla (CSS/Tailwind/Swift/Compose) platform-agnostic senkronize eder. Diff preview + onay + write akışı zorunlu. Her platformda çalışır. Condensed-first: Essentials bölümü %80 case'i kapsar, Advanced sadece edge case'lerde.

atezer/FMCP · 0 tokens

design-engineering

Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…

broomva/skills · 231 tokens

analyze-component-set-figma

Analyze a Figma COMPONENTSET as a state machine for code generation — extract variant axes (state/size/etc.), map state variants to CSS pseudo-classes (hover→:hover, focus→:focus-visible, disabled→:disabled, error→[aria-invalid]), and compute per-variant visual diffs (only what changes per state). Use when generating…

southleft/skills-for-figma · 180 tokens

extract-design

Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…

Manavarya09/design-extract · 140 tokens

s2-docs

Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components. Use when the user mentions Spectrum, S2, React Spectrum, RSP, Spectrum Web Components, or SWC, or names a Spectrum component (Button, Picker, ComboBox, TextField…

adobe/spectrum-design-data · 91 tokens