design-system-drift

Scan codebases for design system drift and generate prioritized reports.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lord-vinayak/orive-reqcap --skill design-system-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-drift
Source: https://github.com/lord-vinayak/orive-reqcap/tree/main/.claude/skills/audit/design-system-drift_
Command: npx skills add https://github.com/lord-vinayak/orive-reqcap --skill design-system-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the detection of design system drift across a codebase, ensuring consistency and preventing accessibility issues.

Core Features & Use Cases

  • Automated Drift Detection: Identifies drift in token, component, pattern, accessibility, and Storybook across a codebase.
  • Prioritized Reporting: Provides a Drift Score and detailed report with severity-weighted findings.
  • Fix Approval: Allows human review and approval before applying fixes.
  • Use Case: Use this Skill during design system audits, component updates, or when introducing new use cases to ensure ongoing compliance.

Quick Start

Run the design-system-drift skill on your codebase to scan for drift and generate a report.

Frequently Asked Questions about design-system-drift

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

FAQPage Schema
How do I detect design system drift in my codebase?

You can automate design system drift detection by scanning your codebase for token, component, pattern, accessibility, and Storybook deviations. This generates a prioritized report featuring a Drift Score and severity-weighted findings for review.

What is a Drift Score in design system analysis?

A Drift Score is a severity-weighted metric generated by analyzing codebase deviations from design system documentation. It quantifies inconsistencies across tokens, components, patterns, and accessibility to prioritize fixes.

Does this design system drift scanner check for Storybook inconsistencies?

Yes, the scanner specifically checks for Storybook drift alongside token, component, pattern, and accessibility drift. It requires access to your codebase and design system documentation to generate its findings.

Can I review and approve design system fixes before they are applied?

Yes, this drift detection process allows for human review and approval before applying fixes. It outputs a detailed report of severity-weighted findings, ensuring you maintain control over codebase modifications.

When should I run an automated design system audit?

You should run a design system audit during component updates, when introducing new use cases, or to ensure ongoing compliance. Running automated drift detection regularly prevents accessibility issues and maintains codebase consistency.