design-system-review
Skill48 starsChanged 15 days agoApache-2.0View on GitHub
Audit apps/web UI for Design System compliance — flags raw px font-sizes, hardcoded/garish colors (hex/rgba glows, decorative gradients), inline styles that bypass tokens, and hand-written components (badges, flow strips, empty states, panels) that should use shared/ui. Use when reviewing UI changes, before committing front-end work, or when asked to "check design system / DS compliance / UI consistency".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- codeotter0201/design-system-skillstheir own version, first seen Nov 8, 2026
- aditya-ariosity/ux-ui-skillstheir own version, first seen Sep 2, 2026
- Gonadotrophic-tangent41/ux-ui-skillstheir own version, first seen Aug 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aditya-ariosity/ux-ui-skills★ 2same name
- codeotter0201/design-system-skills★ 0same name
- Gonadotrophic-tangent41/ux-ui-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 61
Every reusable component under shared/ui/ must be re-exported from shared/ui/index.ts (except app-shell layouts, which are imported …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design System review
Audit the LabelHub web app (apps/web) against the Design System defined in
apps/web/src/shared/ui/README.md and the tokens in apps/web/src/shared/ui/tokens.css.
Report violations with file:line and a concrete fix. Do not auto-fix unless asked.
Scope
By default review the working-tree diff (git diff --name-only + staged). If asked for a full
audit, scan all of apps/web/src. Focus on .tsx and apps/web/src/app/styles.css.
Checks (run these, report every hit)
Run from apps/web/src.
- Raw font-size (must use the type-scale tokens) — any literal px is a violation:
Fix: map to the nearestgrep -nE "font-size:\s*[0-9]" app/styles.css grep -rnE "fontSize:\s*['\"]?[0-9]" --include="*.tsx" .var(--font-size-*)token (display 28 / page-title 22 / section-title 18 / card-title 15 / body 14 / small 13 / caption 12 / micro-label 11). - Hardcoded / garish colors — raw hex/rgba, decorative gradients, glow orbs:
Fix: usegrep -nE "#[0-9a-fA-F]{3,8}\b|rgba?\(" app/styles.css | grep -v "var(--" grep -nE "radial-gradient|linear-gradient" app/styles.css grep -rnE "color:\s*['\"]#|background:\s*['\"]#" --include="*.tsx" .--color-*tokens (*-softfor tints, semantic for text). Removeradial-gradientglow orbs and decorative blue/neon gradients — these are the "low-level AI" look. Functional canvas grids (schema designer dot patterns) are allowed; note them but don't flag as garish. - Non-canonical mono font — must be the token:
grep -nE "monospace" app/styles.css | grep -v "var(--font-family-mono)" - Inline styles that bypass tokens:
Fix: move to a className ingrep -rn "style={{" --include="*.tsx" . | grep -vE "node_modules"styles.css; for truly dynamic values pull fromshared/uitokens. - Hand-written components that should use
shared/ui:
Any direct usage outsidegrep -rn "semantic-tag semantic-tag--" --include="*.tsx" . # -> <StatusBadge tone=...> grep -rnE "flow-strip|flow-node|flow-step" --include="*.tsx" . # -> <FlowStrip steps=...> grep -rnE "<Empty\b" --include="*.tsx" . # -> <EmptyState ...> grep -rnE "role-badge--" --include="*.tsx" . # -> <RoleBadge role=...>shared/ui/is a violation — replace with the component. - New shared component not exported from the barrel:
Every reusable component underls shared/ui/*.tsx | grep -vE "\.test\." grep -n "export" shared/ui/index.tsshared/ui/must be re-exported fromshared/ui/index.ts(except app-shell layouts, which are imported directly by design).
Report format
Group findings by check. For each: file:line · the offending snippet · the one-line fix.
End with: a count per category, and a verdict — PASS (no violations in scope) or
N violations with the top 3 to fix first. If asked, after reporting run:
cd apps/web && pnpm typecheck && pnpm testto confirm the current tree is green before/after fixes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

