Menu

Individual skill

design-system-guardian

0upvotes

Detects hardcoded colors, spacing, typography, widths, and other raw values that should use design-system tokens instead. Use when a project has an established design system/token set and you want to catch drift from it.

skills/ui-ux/design-system-guardian/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Catch places where UI code uses raw/hardcoded values (hex colors, pixel spacing, arbitrary font sizes) instead of the project's established design tokens — the specific class of consistency drift that causes a design system to slowly stop being followed.

## When to Use

- The project has an established design-token system (CSS variables, a theme object, Tailwind config, etc.) and you want to check code against it.
- Reviewing new UI code for token compliance before merge.
- Auditing an existing codebase for accumulated token drift.

Requires knowing (or being told, or being able to find) the project's actual token set — this skill checks *against* an existing system, it doesn't invent one from scratch (for that, see [UI Auditor](../ui-auditor/) for general consistency without an established token baseline).

## What to Analyze