What problem does it solve? Design systems drift over time: naming becomes inconsistent, hardcoded values replace tokens, and components ship without documentation. This Skill provides structured workflows to audit consistency, document components, and design new patterns that fit the existing system. ## Core Features & Use Cases - System Audit: Review naming consistency, token coverage, and component completeness, producing a scored report with prioritized actions. - Component Documentation: Generate documentation covering variants, props, states, accessibility (ARIA roles, keyboard behavior), and do's/don'ts. - Pattern Extension: Design new components with proposed APIs, variants, states, token usage, and open questions for design review. - Use Case: A team notices buttons use three different naming conventions and hardcoded hex colors. Run an audit to get a token coverage table and a prioritized list of fixes, then document the Button component's states and accessibility notes. ## Quick Start Ask the assistant to audit the design system for naming inconsistencies and hardcoded color values across components.
