What problem does it solve? Design documentation written before a build drifts from what actually ships, and undocumented builds leave future work guessing at tokens and rules. This Skill records the design system after the build is finished, grounding every token and rule in the shipped artifact rather than in intentions. ## Core Features & Use Cases - Evidence-Based Design Tokens: Scans stylesheets, custom properties, computed values, spacing rhythm, and the type ramp as actually used, recording only durable system rules. - DESIGN.md and Sidecar Generation: Follows the operating spec in reference/document.md for format, token schema, sidecar, and section order, and updates an existing DESIGN.md by preserving confirmed incumbent decisions. - Defect Guardrails: Refuses to canonize craft-floor violations (invented kickers, hard offset shadows, glyph icons) into system rules, recording them as defects instead. - Use Case: After shipping a new marketing site built with the Impeccable workflow, run this Skill to produce a DESIGN.md that future surfaces can inherit, with a not-canonized line naming the defects the build carries. ## Quick Start Document the design system of the finished build at the project root, writing DESIGN.md at the app boundary using the direction contract and PRODUCT.md as inputs.
