What problem does it solve? Teams building products across multiple screens often end up with inconsistent colors, typography, spacing, and component behavior because there is no shared, project-grounded design system. This Skill produces a coherent visual direction, semantic design tokens, and reusable component rules grounded in the existing repository rather than generic trends. ## Core Features & Use Cases - Design Language Definition: Recommends one coherent visual direction covering color, typography, spacing, elevation, iconography, and motion, tied to product evidence. - Semantic Token Planning: Defines semantic token families (background, foreground, primary, destructive, focus-ring, and more) with purpose, inheritance, and consumption rules. - Component and Content Rules: Specifies component states, resilient content behavior for long labels and localization, responsive breakpoints, and accessibility contracts. - Use Case: A team about to build a dashboard asks the assistant to audit the existing UI and propose a design system. The Skill inspects current tokens and components, then returns a structured brief covering visual direction, tokens, component rules, and a validation plan. ## Quick Start Ask the assistant to audit the current UI and propose a semantic design token system and component guidance for this project without editing any files.
