What problem does it solve? Teams building UIs with the Vibrant visual style often lack consistent, opinionated rules for applying its color palette, typography scale, and spacing rhythm, leading to inconsistent components and accessibility gaps. ## Core Features & Use Cases - Token-Driven Guidance: Anchors every rule to concrete Vibrant tokens such as primary #7C61D4, the 14/16/18/24/32/40 typography scale, and the 2/4/8/12/16/24/32/48 spacing scale. - Component Rule Authoring: Produces component anatomy, variants, states (default, hover, focus-visible, active, disabled, loading, error), and responsive behavior specifications. - Accessibility Acceptance Criteria: Enforces WCAG 2.2 AA requirements including keyboard-first interactions, visible focus states, and 44px+ touch targets. - Use Case: A designer asks for button component guidelines; the Skill outputs token usage, interaction states, anti-patterns, and a QA checklist ready for code review. ## Quick Start Use the vibrant skill to write design-system guidelines for a card component including states, accessibility criteria, and a QA checklist.