/* tokens, styles & components */
--color-primary: #284BD6;
--radius-card: 18px;
grid-template-columns: 2fr 1fr;
@media(max-width: 640px) { ... }Read the code. Recover the design.
Your interface
has a language.
Turn frontend source into a clear DESIGN.md—colors, type, components and layout, described precisely enough to use again.
From implementation
to a usable reference.
The output explains what a design does, not just which CSS values it contains.
Clear Cobalt (#284BD6) Primary actions and links. White, 18px panels with fine borders. A 2:1 layout becomes one column at 640px.
The design, in six dimensions.
01 · Atmosphere
Visual mood, density, color temperature and the intent behind the styling.
02 · Palette & roles
Descriptive names, exact color values and what each color is used for.
03 · Typography
Font families, hierarchy, weights, tracking and readable spacing.
04 · Components
Button, panel, navigation and input patterns—including defined states.
05 · Layout
Widths, grids, spacing rhythm, breakpoints and responsive behavior.
06 · Generation notes
Design language and component prompts for continuing the visual system.
Made for
Teams inheriting a frontend.
Designers documenting an existing interface. Developers moving a visual language between projects. Teams preparing a consistent brief for Stitch.
Know the boundary
Source analysis, not a visual audit.
It cannot prove how a page renders, test accessibility, recover unavailable runtime data or generate a complete app. Inconsistent or missing source styles still need human judgment.
Works with a compatible coding agent that can read and write files. References cover React/Tailwind, Vue, Svelte, Angular and plain CSS. The local workflow needs no Stitch account; optional service integration requires separate setup.
Independent Codex run on one synthetic fixture
Named source-color mappings checked
Bundled framework references
One independent Codex agent read the original skill and the two-file HTML/CSS fixture without consulting earlier outputs. Eleven structural/source-alignment assertions passed; they are not an accuracy rate. No build, browser render or other framework was tested.