What problem does it solve? Teams building interfaces with a hand-drawn, pencil-sketch aesthetic often lack consistent, documented rules, leading to inconsistent spacing, colors, and component states across the product. ## Core Features & Use Cases - Design Token Foundations: Defines the Sketch palette (teal primary #1DAD97, cream secondary #F4EDE0), typography (Delicious Handrawn, JetBrains Mono), and spacing scale (4/8/12/16/24/32). - Component Rule Authoring: Produces component anatomy, variants, states (hover, focus-visible, disabled, loading, error), and responsive behavior guidance. - Accessibility & QA Gates: Enforces WCAG 2.2 AA requirements, testable acceptance criteria, anti-patterns, and a code-review QA checklist. - Use Case: A designer asks for button guidelines in the Sketch style and receives token-anchored rules covering states, keyboard interaction, and migration notes for legacy components. ## Quick Start Use the sketch skill to write design-system guidelines for a card component following the hand-drawn Sketch style.