What problem does it solve? Deciding whether a finished design-system document is good enough to build from is subjective and error-prone. This Skill acts as an acceptance gate: it judges a design-system document (or a versioned amend delta) against a fixed, single-sourced bar covering DTCG design tokens, component completeness, catalog coverage, WCAG 2.2 AA accessibility, internationalization, and governance, then emits a machine-parseable verdict with actionable findings. ## Core Features & Use Cases - Checklist-based review: Judges 13 named conditions — principles, DTCG intent-named tokens, foundations, theming, per-component five-part specs, API consistency, catalog coverage, patterns, layout/i18n, numeric WCAG 2.2 AA accessibility, voice, governance, and groundedness. - Delta-scoped amend review: For versioned changes, reviews only the diff — checking scope-confinement, token ripple/regression, semver accuracy, and deprecation safety. - Machine-parseable output: Emits exactly VERDICT: approve or VERDICT: revise plus actionable findings (failed condition, location, concrete fix). - Use Case: Before wireframing begins, run this Skill on a finished design-system markdown document to confirm an engineer can build a consistent, accessible UI from it — catching issues like a Button spec hard-coding #1A73E8 instead of referencing a semantic token. ## Quick Start Review the attached design-system document against the buildability bar and give me the verdict with any blocking findings.
