google-stitch-extract-frontend-design-systemlisted

# Extract Frontend Design System ## Overview Reverse-engineer the design system from source without requiring a working build. Produce an evidence-backed `DESIGN.md` that another agent can use without rereading the repository. ## Workflow 1. **Map coverage.** Identify frameworks, styling systems, package boundaries, entry points, global styles, theme files, shared components, and representative pages. Record what was inspected and what was unavailable. 2. **Load the relevant reference.** Read only the matching guide: [React/Tailwind](references/react-tailwind.md), [Vue](references/vue.md), [Svelte](references/svelte.md), [Angular](references/angular.md), or [plain CSS/Sass/Less](references/plain-css.md). Use multiple guides only for a mixed stack. 3. **Collect evidence.** Extract declared and actually used colors, type styles, spacing, radii, borders, elevation, breakpoints, layout primitives, imagery, motion, and component states. Cite file paths, selectors, token names, or components. 4. **Normalize carefully.** Separate aliases from duplicates, declared tokens from one-off values, and global rules from component exceptions. Flag near-duplicates and contradictions; do not silently choose a winner. 5. **Explain intent.** Label each conclusion as **Observed**, **Inferred**, or **Unknown**. Infer atmosphere and hierarchy only from repeated evidence. Never invent missing fonts, breakpoints, states, or brand rationale. 6. **Write the contract.** Create or update root-level `