Identify where a design system has diverged from its original intent across the whole system — components implemented differently to spec, tokens overridden locally, patterns forked across teams. This is a system-wide sweep for divergence patterns, NOT a single-component spec comparison. Trigger when someone says: find drift, where has the system diverged, design code inconsistency, what's out of sync, where are teams going off-system, component drift, or anything about identifying gaps between design system intent and actual implementation. Do NOT trigger for checking one specific component against its design spec — use design-to-code-check for that.
$npx -y skills add murphytrueman/design-system-ops --skill drift-detectionInstalls into the current project.
Run `npx skills use "https://github.com/murphytrueman/design-system-ops" --skill "murphytrueman/design-system-ops/drift-detection"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/murphytrueman/design-system-ops" that are relevant to the current task. Run `npx skills add "https://github.com/murphytrueman/design-system-ops"` and select the relevant skills, then follow their instructions.