What problem does it solve? Teams lack a single canonical record of adopted visual and interaction rules, so agents and developers build inconsistent screens and cannot tell settled design policy from accidental implementation details. ## Core Features & Use Cases - Canonical design pages: Writes .specs/design-guidelines.md or thin per-package deltas that separate adopted policy, observed implementation, and verified enforcement. - Structured discovery: Runs greenfield or existing-project discovery with focused question rounds, producing a reviewable summary before any policy is written. - Accessibility and acceptance criteria: Defines a Design definition of done with WCAG 2.2 targets, evidence labels (verified, failed, not tested, not applicable), and reusable evidence records. - Use Case: Adopting an existing app's design system into specs: the skill inspects tokens, themes, and components, confirms intent on inconsistencies, and documents settled rules while listing implementation gaps in Open questions. ## Quick Start Ask the agent to create design guidelines in .specs for your project, describing the audience, platforms, and any existing brand or UI assets.
