๐Ÿงช
QualityHTML

Design To Code Check

by murphytrueman

Design To Code Check is a Quality skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22
claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills
Install in seconds
Install Design To Code Check
Copy Design To Code Check into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/design-to-code-check ~/.claude/skills/design-to-code-check

Requires Node.js. Downloads this skill only โ€” not the rest of the repository โ€” into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skillโ€™s own directory into your skills folder yourself.

In this catalog

Source file
skills/design-to-code-check/SKILL.md in murphytrueman/design-system-ops
Installs to
~/.claude/skills/design-to-code-check
Collection
One of 25 skills cataloged from this repository
Category
Quality โ€” 1817 skills

What Design To Code Check does

Design To Code Check reviews a single component or screen against its design specification and flags mismatches by dimension and severity. Use it when comparing a design to the built implementation or checking what differs between them.

Design To Code Check is cataloged under Quality on DirSkills. Design To Code Check comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

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.

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.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Design To Code Check

  • What else does murphytrueman publish alongside Design To Code Check?

    Design To Code Check is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Design To Code Check does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.

  • How does Design To Code Check compare to other Quality skills?

    Design To Code Check ranks #1692 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Design To Code Check against them. Open each page to compare what they document and how they install.

More from murphytrueman/design-system-ops

Design To Code Check is one of 25 skills cataloged on DirSkills from murphytrueman/design-system-ops.

See all 25 skills โ†’
๐Ÿค–
2h ago

AI Component Description

AI Component Description generates six-section prose descriptions for components so LLMs can understand purpose, props, composition, accessibility, and examples. Use it when writing Figma MCP descriptions or other text meant to make components legible to Claude and similar agents.
AI Engineering
1767
โ™ฟ
2h ago

Accessibility Per Component

Accessibility Per Component runs a structured accessibility audit on a single design system component. It checks keyboard use, screen reader behavior, colour contrast, focus, and ARIA against WCAG 2.1 AA.
Quality
1767
๐Ÿ“ˆ
2h ago

Adoption Report

Adoption Report separates design system coverage from actual adoption, with trend direction and risk flags. Use it when you need to measure which teams are using the system and where usage is low or declining.
Data
1767
๐Ÿ—‚๏ธ
2h ago

Backlog Generator

Backlog Generator turns audit findings into sprint-ready work items with titles, effort estimates, acceptance criteria, and rationale. Use it when you need to convert review output into actionable tickets instead of running an audit or defining contribution guidelines.
Automation
1767
โš™๏ธ
2h ago

CI/CD Integration

CI/CD Integration generates pipeline files that automate design system checks such as token validation, component linting, accessibility scans, visual regression, and release gating. Use it when you need CI to enforce the same rules audit skills check manually.
DevOps
1767
๐Ÿ“ฃ
2h ago

Change Communication

Change Communication produces release notes, migration guidance, and team announcements for design system changes that have already been decided. Use it when you need to communicate a patch, enhancement, breaking change, or system update to consuming teams.
Writing
1767