design-mdlisted

# DESIGN.md Design Systems ## Purpose DESIGN.md records a design system as machine-readable YAML tokens plus a prose rationale, so an implementing agent stops using its own defaults. Three gaps stand between an agent and a usable file: 1. **Syntactic** — schema, references, the eight body sections. Closed by `references/spec-anatomy.md`. 2. **Procedural** — verifiable output handed back unverified. Closed by `scripts/lint` and Route 4. 3. **Substantive** — a *valid* file is not a *useful* one. Closed by `references/anti-slop.md`, and by nothing else. The third bites hardest because nothing reports it: a file of framework defaults, `system-ui`, one radius and four truisms lints at zero errors. Toolchain: `@google/design.md@0.4.0` (Apache-2.0, Google LLC), run via `npx`. ## When to Use This Skill Use this skill when the user: - asks for a DESIGN.md, a design system, a token file, or design tokens; - asks to extract a palette from a screenshot, a mockup, or an image, or to derive a system from a brand brief, a codebase, or a tailwind config; - asks to audit, repair or lint an existing DESIGN.md, export its tokens to Tailwind v3/v4, DTCG or CSS custom properties, or compare two revisions; - says the output looks generic and asks to deslopify it, or writes any of дизайн-система, фирменные цвета, единый стиль, извлеки палитру, по скриншоту. Out of scope: images, logos, component implementation, palettes derived from one seed colour. This skill produces the specificati