drift-detection

Detect and classify design system drift across visual, behavioral, API, and token dimensions.

155|7|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/murphytrueman/design-system-ops --skill drift-detection-murphytrueman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift-detection
Source: https://github.com/murphytrueman/design-system-ops/tree/main/skills/drift-detection
Command: npx skills add https://github.com/murphytrueman/design-system-ops --skill drift-detection-murphytrueman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and classifies deviations between a design system's intended state and its actual implementation across various products, helping to maintain consistency and reduce technical debt.

Core Features & Use Cases

  • System-wide Audit: Detects visual, behavioral, API, and token drift across components and patterns.
  • Root Cause Analysis: Classifies drift as intentional divergence, version lag, accidental drift, misunderstanding, or system gap.
  • Prioritized Remediation: Provides actionable recommendations, including migration plans and contribution suggestions.
  • Use Case: A senior engineer wants to understand how much a product's UI has drifted from the central design system over the last quarter. This Skill will scan the codebase and design files to report on all inconsistencies, categorizing them by severity and type.

Quick Start

Use the drift-detection skill to find where the design system has diverged across the entire codebase.

Frequently Asked Questions about drift-detection

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

FAQPage Schema
How do I audit my codebase for design system drift and inconsistencies?

Design system drift is detected by scanning your codebase and Figma sources to identify visual, behavioral, API, and token deviations, which are then classified by root cause and severity.

What causes design token drift between Figma and my code repository?

Design token drift between Figma and code repositories is classified by this Skill as intentional divergence, version lag, accidental drift, misunderstanding, or system gaps, providing a root cause analysis for each inconsistency.

How do I classify component inconsistencies as intentional divergence or accidental drift?

Component inconsistencies are classified by analyzing deviations between the intended design system state and actual implementation, categorizing them as intentional divergence, accidental drift, version lag, misunderstanding, or system gaps.

Can I track design system migration debt and prioritize remediation for UI inconsistencies?

Yes, you can track migration debt and prioritize remediation. This Skill models migration debt and provides prioritized, actionable remediation paths including contribution suggestions and migration plans.

Does this design system component audit work with Figma and code repositories?

Yes, the component audit works with Figma and code repositories. The Skill uses these configurable sources to perform a system-wide audit across components and patterns, detecting visual, behavioral, and token deviations.

What is the best way to reduce technical debt from design system inconsistencies?

The best way to reduce technical debt from design system inconsistencies is to identify and classify deviations across visual, behavioral, API, and token dimensions, then follow prioritized remediation paths and migration plans.