- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add reticlehq/reticle --skill design-system-compliance -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add reticlehq/reticle --skill design-system-compliance -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add reticlehq/reticle --skill design-system-compliance -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add reticlehq/reticle --skill design-system-compliance -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/reticlehq/reticle/tree/HEAD/skills/design-system-complianceFrom the publisher
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 set up? Follow the reticle skill: it installs Reticle, asks the user before init changes the app's files, and proves one flow.
reticle_look({ action: "page", sessionId, mode: "interactive" })
reticle_look({ action: "element", sessionId, ref })
inspect returns a theme report per element:
Read tokenCount first. Zero tokens means there is nothing to comply with, and every "pass" below it is vacuous.
The same call answers the questions a screenshot cannot:
occluded: covered by an overlay. It renders, and no user can click it.box: 0×0 is 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.
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.
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.
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".
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
---name: design-system-compliancedescription: Check that the UI you actually rendered uses the design system, by reading computed styles in the running app…---# skills/design-system-compliance/SKILL.mdOverview
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.
FAQ
Download skills/design-system-compliance/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/reticlehq/reticle.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.