设计与 UI
Roast My Design System
A Claude Code/Codex skill that audits design systems with a health score, receipts, prioritized fixes, and generated rules to prevent regressions.
pencilrebel · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add pencilrebel/roast-my-design-system技能说明
roast-my-design-system
A Claude Code skill that roasts your repo's design system with real data.
Run this skill on your codebase and get, in about a second:
- A health score you can defend in a meeting. 0-100, deterministic, benchmarked against Ideal Design System norms, 30 scanned public repos and 10 reputable design systems (Primer, Polaris, Carbon, shadcn/ui…).
- Per-package scores for monorepos. One blended number hides which package is the problem:
packages/uiscores 80 whileapps/webscores 40, and now you can see it. - The receipts behind it. Every colour and its near-identical twin, every spacing value, typeface, duplicated or never-imported component, inline style and !important, with real file paths, in one self-contained HTML report you can open, Slack or email.
- The first fixes ranked by payoff. A "Where to start" list derived from your own numbers: keep the report as the audit, or hand it to Claude as the punch list for the fix.
- Rules that stop the mess coming back. A generated
design-system-rules.mdfor your CLAUDE.md or .cursor/rules: canonical components, your token file, known duplicates to avoid, so your AI agent follows your system instead of guessing at it.
Why this exists
Your AI agent (Claude, Cursor, Copilot) builds UI by imitating what's already in your repo. If your repo has 112 colours and four Button implementations, your agent guesses which one is canonical, and it picks wrong half the time. That's why AI-generated UI looks almost-but-not-quite right. The first step to fixing it is seeing the mess measured.
Example use cases
- Pre-refactor audit. Run
/roast-my-design-systembefore a design-system cleanup to get the measured baseline: every colour, spacing value, duplicated compon