What problem does it solve? Most codebases have an implicit design system that is never written down, making it impossible to enforce visual consistency or detect drift. This legacy workflow reads the actual code to document the patterns that already exist. ## Core Features & Use Cases - Pattern Extraction: Surveys Tailwind configs, CSS custom properties, theme objects, and token files to extract spacing scales, color palettes, typography scales, and component patterns. - Contract Generation: Produces a structured docs/DESIGN_SYSTEM.md document covering palette, semantic color roles, type hierarchy, layout conventions, and responsive behavior. - Inconsistency Detection: Flags places where the codebase disagrees with itself, creating a backlog for convergence work. - Use Case: After a redesign introduces divergent patterns, run this workflow to document what the code actually does and identify which deviations need alignment. Note: This skill is deprecated. Prefer the current ui-* reference skills and the design-expert/design-* reference model for new UI and design work. ## Quick Start Ask the agent to run the legacy design system extraction workflow to survey this codebase and write the findings to docs/DESIGN_SYSTEM.md.