arib-check-design

To audit frontend codebase for design system compliance, run the skill against your components directory to perform pattern matching and identify unauthorized token usage, component drift, and typography inconsistencies.

Detecting raw color literals bypassing design tokens involves scanning source code for forbidden hex or rgb values. The skill enforces token discipline by matching patterns against your centralized design constraints to prevent visual drift.

To prevent component drift from established UI primitives like shadcn, the skill validates component baselines by identifying unauthorized library imports and checking for deviations from your project's standard UI architecture.

The UI audit works with tailwind styling configurations by operating across web-based component libraries and styling setups. It uses standard grep utilities to verify typography stacks and motion patterns respect project standards.

Verifying motion patterns respect user preferences is handled through accessibility guardrails during the design audit. The skill checks your source code to ensure motion implementations remain compliant with established accessibility constraints.

Performing a UI source code audit requires access to your project architecture directory and standard grep utilities. These dependencies allow the skill to execute pattern matching against your defined design system contract.