detect-design

Detect drift between design tokens and their codebase usage.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill detect-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-design
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/detect-design
Command: npx skills add https://github.com/parhumm/jaan-to --skill detect-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect design system drift by identifying mismatches between token definitions and their real usage in code, enabling teams to keep a consistent design language and governance across repositories.

Core Features & Use Cases

  • Token inventory across design tokens, Tailwind themes, and CSS variables to reveal the token landscape and naming conventions.
  • Drift detection that pairs token definitions with actual usage in components, surfacing inconsistencies with evidence blocks.
  • Governance signals detection through analysis of Storybook configuration, MCP readiness, and token/documentation signals.
  • Use Case: Audit a large mono-repo to surface token-usage drift and prepare a prioritized plan for token updates and design-system governance.

Quick Start

Run detect-design on your project to produce a drift report and token inventory.

Frequently Asked Questions about detect-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect design system drift in a monorepo?

Detect design system drift by scanning token files, theme definitions, and component usage to identify mismatches. It performs token inventory and drift detection, producing structured outputs and evidence blocks that document inconsistencies between definitions and actual code usage.

What is design token inventory and how does it work?

Design token inventory maps the token landscape by scanning design tokens, Tailwind themes, and CSS variables to reveal naming conventions. It catalogs all defined tokens across the codebase to establish a baseline for comparing against actual component implementation.

Can I audit Tailwind theme tokens against component usage?

Yes, you can audit Tailwind theme tokens against component usage. The drift detection pairs token definitions with actual usage in components, surfacing inconsistencies with evidence blocks that highlight where the codebase deviates from the defined theme.

How do I check design system governance signals in my codebase?

Check design system governance signals by analyzing Storybook configuration, MCP readiness, and token documentation signals. It scans for these signals to evaluate the maturity and consistency of design system governance across the repository.

What is the best way to audit CSS variables for brand consistency?

Audit CSS variables for brand consistency by scanning token definitions, component usage, and brand assets. This approach surfaces mismatches between defined variables and their real usage, enabling teams to maintain a consistent design language and governance.

Does design token drift detection work for large monorepos?

Yes, design token drift detection is built for large monorepos containing token files, theme definitions, and component usage. It scans the repository to surface token-usage drift and produces a prioritized plan for token updates and governance.