onsystem

Keeps coding agents on your design system: catches palette colors, native elements and APIs your system lacks, at every edit and pull request, with the fix. Set

What is onsystem?

Keeps coding agents on your design system: catches palette colors, native elements and APIs your system lacks, at every edit and pull request, with the fix. Set it up once in your design-system package; every app in your monorepo gets it.

Overview of onsystem

What it is

onsystem is a tool that keeps coding agents on your design system. It catches palette colors, native elements, and APIs your system lacks at every edit and pull request, with the fix. It runs locally and works alongside @shadcn/lint. It is built for design-system and platform teams with a React design-system package; a shadcn/ui app is the zero-config demo. It was formerly @dgesteves/design-system-mcp.

Key features

  • Catches palette colors, native elements, and APIs your design system lacks, at every edit and pull request, with the fix.
  • Reads your components, cva and tv variants, parts, and tokens from source using the TypeScript compiler, and checks .tsx and .jsx files against them.
  • Every finding has a rule ID, a location, and the fix.
  • Tokens come from your stylesheets, DTCG 2025.10 files, or a DESIGN.md; onsystem export writes them out as either.
  • Integrates with Claude Code via a plugin that brings a hook, MCP server, and skill; also works with Cursor, VS Code, and other agents.
  • Supports CI integration: install as dev dependency, accept existing findings with a baseline, and fail pull requests only on new ones.
  • Provides a GitHub Action that runs the same check, honours the baseline, and annotates only the lines a pull request changed.

Use cases

  • Ensuring coding agents write UI components that match the design system, rather than using hardcoded colors, native elements, or non-existent components.
  • Catching design system violations during development (at every edit) and in pull requests.
  • Onboarding new apps in a monorepo: set up once in the design-system package, every app gets the checks automatically.
  • Integrating into CI/CD pipelines to enforce design system compliance with baseline support for existing code.

Getting started

sh npx -y onsystem inspect # what it found; --explain says why npx -y onsystem check . # the same check the agent and CI run npx -y onsystem init # write the config, and offer a baseline For Claude Code plugin: /plugin marketplace add dgesteves/onsystem /plugin install onsystem@dgesteves For CI: sh npm install --save-dev onsystem npx onsystem check . --update-baseline # writes onsystem.baseline.json: commit it Requires Node.js 20.19 or later.

License and pricing

License: MIT. The project is open source.

Based on the project's public README and repository metadata.

Add this badge to your README

Featured on YunoDB Badge styles & help

Maintain this project? Show that it is featured on YunoDB.

Markdown[![Featured on YunoDB](https://yunodb.com/badge/dgestevesonsystem.svg)](https://yunodb.com/tools/dgestevesonsystem?utm_source=github&utm_medium=badge)
HTML<a href="https://yunodb.com/tools/dgestevesonsystem?utm_source=github&utm_medium=badge"><img src="https://yunodb.com/badge/dgestevesonsystem.svg" alt="Featured on YunoDB" height="20"></a>