What problem does it solve? Teams building approachable, friendly interfaces often lack consistent design-system documentation, leading to inconsistent spacing, low-contrast text, and ambiguous component states across products. ## Core Features & Use Cases - Token-Driven Foundations: Defines color tokens (primary #F2D9DC, secondary #D9F2D8, semantic states), typography scales (14/16/18/24/32/40 with Noto Serif Display and Space Mono), and compact spacing rules. - Component Rule Authoring: Produces implementation-ready guidance covering component anatomy, variants, states (hover, focus-visible, disabled, loading, error), and responsive behavior. - Accessibility Enforcement: Embeds WCAG 2.2 AA requirements, keyboard-first interactions, and testable acceptance criteria into every guideline. - Use Case: A designer asks for button component rules; the Skill outputs token-anchored specs with states, anti-patterns, migration notes, and a QA checklist for code review. ## Quick Start Use the friendly skill to write design-system guidelines for a card component including states, accessibility criteria, and anti-patterns.