reticlehq/reticle

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.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/reticlehq/reticle --skill design-system-compliance

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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_snapshot({ sessionId, mode: "interactive" })
reticle_inspect({ sessionId, ref })

inspect returns a theme report per element:

FieldWhat it tells you
offThemethe headline. True when a set, opaque color matches no token in the palette: a violation worth fixing
colorTokens / backgroundTokensevery token whose resolved value is this color. Empty means off-palette
colorToken / backgroundTokenthe unambiguous match, or null when several tokens share the color. null here is an abstention, not a violation: read the plural field
tokenCounthow 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
themeScopethe 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×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.

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_feedback with kind: "gap".

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
reticlehq
커뮤니티

reticle

Install, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns a verdict with the file:line to fix. Use when the user asks to set up or install Reticle, when a user-facing change needs proving before you call it done, when a test passes but the UI is broken, or when the user types /reticle.

1시간 설치 수
1
GitHub Stars
1.3천
업데이트
10월 30일
reticlehq
커뮤니티

audit-my-app

Sweep a whole running web app for what is broken, without writing a script or knowing the codebase. Clicks every reachable control and reports dead buttons, console errors, failed requests, and places where the API and the screen disagree. Use on an unfamiliar codebase, before a release, after a big merge or dependency bump, when the user asks for a smoke test or a health check, or when someone says "just check everything still works".

1시간 설치 수
1
GitHub Stars
900
업데이트
9월 26일
reticlehq
커뮤니티

debug-broken-ui

Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page renders blank or stale, a modal will not close, or the user says "it's broken" and the code review says it is fine.

1시간 설치 수
1
GitHub Stars
900
업데이트
9월 26일
reticlehq
커뮤니티

fix-what-i-pointed-at

Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or PM has left feedback in the UI, or when the user describes a problem as "that button there" without saying which file.

1시간 설치 수
1
GitHub Stars
900
업데이트
9월 26일