design-system-compliance
Check that the UI you actually rendered uses the design system, by reading computed styles in the running app against the project's design tokens. Catches hardcoded hex colors, off-palette backgrounds, invisible or unusable controls, and animations that never ran.
Install / Use
npx skills add reticlehq/reticle --skill design-system-complianceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Our assessment of design-system-compliance
design-system-compliance scores 85/100 on our quality scale, 161st of 262 Design skills we index.
Its SKILL.md is 4.0 KB long, split into 6 sections with 2 code examples: a solid amount of guidance for an agent.
With 1,271 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 10 days ago, so design-system-compliance is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
design-system-compliance compared with similar skills
All 4 of these similar skills score higher than design-system-compliance; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| design-system-compliance (this skill)by reticlehq | 85 | 1.3k | 10d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
Frequently asked questions
- How do I install design-system-compliance?
- Run
npx skills add reticlehq/reticle --skill design-system-compliance. The install tabs above show the steps for each supported agent. - Which AI agents does design-system-compliance work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is design-system-compliance safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is design-system-compliance still maintained?
- The repository was last updated 10 days ago, so design-system-compliance is actively maintained.
Skill content
View source on GitHubname: design-system-compliance description: Check that the UI you actually rendered uses the design system, by reading computed styles in the running app against the project's design tokens. Catches hardcoded hex colors, off-palette backgrounds, invisible or unusable controls, and animations that never ran. Use after building or restyling a component, when a design review is wanted, when a UI looks slightly off but nobody can say why, or when a design system exists and nothing checks whether the code follows it. license: Apache-2.0 metadata: version: 3.5.0 homepage: https://www.reticle.sh repository: https://github.com/reticlehq/reticle
Does the rendered UI actually use the design system?
Reading the source tells you what the component asks for. It cannot tell you what the browser resolved: a token overridden three layers up, a hardcoded #3b82f6 that happens to look close, a dark-theme scope that never applied. That answer only exists in the running page.
Reticle reads computed styles in the live app and compares them against the project's tokens. Not installed? RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init, then the install-and-verify skill.
The check
reticle_look({ action: "page", sessionId, mode: "interactive" })
reticle_look({ action: "element", sessionId, ref })
inspect returns a theme report per element:
| Field | What it tells you |
| --- | --- |
| offTheme | the headline. True when a set, opaque color matches no token in the palette: a violation worth fixing |
| colorTokens / backgroundTokens | every token whose resolved value is this color. Empty means off-palette |
| colorToken / backgroundToken | the unambiguous match, or null when several tokens share the color. null here is an abstention, not a violation: read the plural field |
| tokenCount | how many tokens resolved under the active theme. 0 means the app declares no palette, and offTheme is never asserted: report that rather than a clean bill of health |
| themeScope | the theme active at capture (e.g. .dark), so two inspects taken minutes apart are comparable at all |
Read tokenCount first. Zero tokens means there is nothing to comply with, and every "pass" below it is vacuous.
Beyond color: is the control actually usable?
The same call answers the questions a screenshot cannot:
occluded: covered by an overlay. It renders, and no user can click it.box:0×0is present-but-invisible, the most common "it's there, I can see it in the DOM" bug.styles.opacity/styles.cursor: the difference between disabled-looking and disabled.source: { file, line }: where to go and fix it.
A design review that only compares colors passes a button nobody can press.
Animations
reticle_run({ tool: "reticle_animations", args: { sessionId } })
Returns running and recently completed animations with their targets and timing. Two things worth checking after any motion work: an animation you added that never appears here did not run, and one whose duration does not match the token is off-spec. Both look identical in a screenshot.
Report violations as locations, not opinions
For each element that failed, give the file:line from inspect and the specific fact: "background #3b82f6 matches no token; the palette has --color-primary at #2563eb". A design-review comment without a location is a task someone else has to redo.
What this is not
This checks compliance with the tokens the project declares. It is not an opinion about whether the design is good, and it is not an accessibility audit. Contrast ratios, focus order and screen-reader semantics are a different job, and claiming them here would be a false green of exactly the kind this repo exists to prevent.
Everything else, one page at a time: curl https://docs.reticle.sh/llms.txt. Design token check missing something you needed? reticle_session { action: "feedback" } with kind: "gap".
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
