Extract a design system from code with AI
Read the styles already in a frontend and document colour roles, typography, components and responsive behaviour in a local DESIGN.md file.
To extract a design system from code with AI, give stitch::extract-design-md access to the frontend you want to document. Teams often inherit a site whose original mockups no longer match the implementation. A colour recorded from a screenshot might look right while missing the distinction between a link, a selected tab and a primary action.
The workflow inspects the framework, follows its styling conventions and checks how components actually use the available values. It pulls the findings into a design document that another designer or agent can read. Source coverage matters: if a component loads its theme from a separate package, that project's visible code may tell only part of the story.
What it does
- Map frontend colours to their functional roles.
- Extract font families, weights and typographic hierarchy.
- Describe button, input and card treatments.
- Record spacing and responsive breakpoints.
- Write a local design guide for future screens.
Install and use
- Install the Stitch design skill in a supported agent and allow local read access to the source and write access to the project. Extraction needs no live Stitch account.
- Ask “Document the shop's button colours, card spacing and mobile headings from its current frontend.”
- Compare .stitch/DESIGN.md with representative screens. Upload to Stitch separately if the team wants a remote design system.
FAQ
Source
Made by Google Labs Code. Original skill: stitch::extract-design-md, published on GitHub under the Apache-2.0 licence.
View on GitHub