MCP server

Roast My Design System MCP: Scan, Score and Guard a Codebase

Roast My Design System scans a codebase for missing design rules, scores it 0 to 100, and runs an MCP server that answers an agent live while it edits.

Run
npx roast-my-design-system@latest --mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is Roast My Design System?

Roast My Design System is an MCP server bundled in the roast-my-design-system npm package. Run it once for a 0 to 100 health score and a ranked list of missing or inconsistent rules, or run it with --mcp so an agent gets live component and token answers while editing, plus a check before a file is saved.

Roast My Design System is an npm package that scans a front-end repo for design system gaps, then exposes the same knowledge to an agent through an MCP server. A plain run with no flags writes a report; adding --mcp starts the server instead.

The report ranks fixes by impact and compares the repo against a set of real-world benchmarks, so a team sees not just what is missing but how far off a healthy baseline it is.

What changes once it is running

  • Before writing a new component, an agent can call a tool for existing canonical components and their usage examples instead of inventing a duplicate.
  • Hardcoded colors, spacing and other raw values get mapped back to the project's own design tokens rather than left as magic numbers.
  • A validate tool checks a file before it saves, and a review tool checks only the files changed in the current git diff.
  • Rules the scan found get written out to a design-system-rules.md file that any agent file can point to.

Framework and library coverage

The scan reads React, Next.js, Vue, Angular, Svelte and plain web components, and recognizes design systems built on Tailwind, shadcn/ui, MUI, Mantine, Chakra UI and Ant Design. It runs read-only and reports no telemetry calls.

Who it is for

Best for

  • Teams whose agents keep inventing one-off components or colors instead of reusing what the design system already has.
  • A CI step that fails a pull request when changed files break design system rules, using the SARIF output for code scanning.
  • Anyone who wants a single health score to track as a codebase grows.

Not for

  • If what you need is a one-time written audit score for a design system, Design System Audit Skill covers that score and fix report directly.
  • When the task is a written design critique of one screenshot instead of live repo rules, Impeccable Critique gives that scored review.
  • When the gap is accessibility fixes rather than design token drift, Fixing Accessibility Skill handles that audit and the small edits after it.
  • When you want line-level linter output scored across weighted dimensions for one file, UI UX Suite MCP gives that design linter detail.

Use it with UiChemy

The server keeps front-end code consistent with an existing design system as an agent writes it. For turning that same page into an editable WordPress build, UiChemy Composer and AI to WordPress cover the other half. Click Get Started on uichemy.com.