SkillAgentSearch skills...

stitch::extract-design-md

Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework.

Install / Use

npx skills add google-labs-code/stitch-skills --skill extract-design-md

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Design

Supported Platforms

Universal

Our assessment of stitch::extract-design-md

stitch::extract-design-md scores 90/100 on our quality scale, 89th of 260 Design skills we index (top 35%).

Its SKILL.md is 14 KB long, well organised into 46 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

With 8,363 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
18/20
Description
15/15
Adoption
17/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-15 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

stitch::extract-design-md compared with similar skills

All 4 of these similar skills score higher than stitch::extract-design-md; compare them before choosing.

SkillScoreStarsUpdatedFormat
stitch::extract-design-md (this skill)by google-labs-code908.4k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install stitch::extract-design-md?
Run npx skills add google-labs-code/stitch-skills --skill "stitch::extract-design-md". The install tabs above show the steps for each supported agent.
Which AI agents does stitch::extract-design-md work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is stitch::extract-design-md safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is stitch::extract-design-md still maintained?
The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: stitch::extract-design-md description: >- Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework. Analyzes component files, stylesheets, Tailwind configs, theme definitions, and design tokens to produce a rich, Stitch-compatible design system document. Use this skill whenever the user wants to reverse-engineer a design system from an existing codebase, audit the visual language of a project, extract design tokens from source files, or understand the styling patterns in a frontend repo — even if they just say "what does this app look like?" or "pull out the design from this code." allowed-tools:

  • "stitch*:*"
  • "Bash"
  • "Read"
  • "Write"
  • "web_fetch"

Extract Design System from Frontend Code

Analyze frontend source code to extract a comprehensive design system document (DESIGN.md) that captures the project's visual language — colors, typography, spacing, component patterns, and layout principles — directly from the source files, without needing to build or render the application.

Why This Exists

The design-md skill works from rendered HTML. But often you have a codebase and want to understand its design system before you can even run the app — maybe dependencies are missing, the build is broken, or you just want a quick audit. This skill reads the source files themselves: stylesheets, component files, theme configs, and Tailwind setups. It's faster and works anywhere.

When to Use

  • User has a frontend codebase and wants to extract or document its design system
  • User wants to migrate a project's visual identity into Stitch
  • User asks to "audit the styling" or "understand the design language" of a repo
  • User wants to create a DESIGN.md from existing source code
  • The app can't be built/rendered but the source is available
  • User wants to unify or reconcile inconsistent styles across a codebase

Prerequisites

  • Access to the frontend project's source directory
  • No build or runtime dependencies needed — this skill reads source files only

Workflow

Phase 1: Project Discovery

Start by understanding what you're working with. This determines which extraction patterns to use.

1. Detect the Framework and Stack

Scan the project root for telltale files:

| Signal File | Framework / Tool | |:---|:---| | package.json with react | React / Next.js | | package.json with vue | Vue / Nuxt | | package.json with svelte | Svelte / SvelteKit | | package.json with @angular/core | Angular | | tailwind.config.js/ts | Tailwind CSS | | postcss.config.js | PostCSS pipeline | | styled-components or @emotion in deps | CSS-in-JS | | .css / .scss / .less files only | Plain CSS / SASS | | theme.js / theme.ts / tokens.js | Design token files |

Read package.json first — it reveals the framework, CSS tooling, and any design-token libraries (e.g., style-dictionary, @chakra-ui/react, @mui/material, ant-design). This context tells you where to look for styling information.

2. Map the Source Tree

Identify the key directories and files you'll analyze:

src/
├── components/     ← Component-level styles
├── styles/         ← Global stylesheets
├── theme/          ← Theme definitions, tokens
├── assets/         ← Fonts, images
├── app.css         ← Root styles
└── index.css       ← Entry CSS

Also check for:

  • tailwind.config.js / tailwind.config.ts — Custom colors, fonts, spacing
  • globals.css / global.css — CSS custom properties (variables)
  • Any theme.* or tokens.* files
  • Component library config (e.g., chakra-theme.ts, vuetify.config.ts)

3. Read Framework-Specific Guidance

Consult the appropriate reference for extraction patterns:

These references contain framework-specific patterns for locating colors, typography, spacing, and component styles. Read the one that matches before proceeding.


Phase 2: Deep Extraction

Work through each design dimension systematically. For each one, gather raw data from the source files, then synthesize it into descriptive language.

The goal isn't to dump every CSS property — it's to understand the intent behind the styling choices and describe them in human, editorial language that another designer (or Stitch) can use to recreate the same visual feel.

1. Visual Theme & Atmosphere

Read the broadest styling first to understand the overall mood:

  • Root background: What's the body or root element background? Light cream (#f-range) signals airy/clean; dark (#0-#2 range) signals moody/dramatic.
  • Whitespace philosophy: Are spacing values generous (32px+) or tight? Check padding/margin values on root containers, section wrappers, and card components.
  • Density: Count the components per page/section. Few with space = minimal; many packed tight = information-dense.
  • Color temperature: Are the neutrals warm (creams, tans) or cool (blue-grays, slates)?
  • Overall feel: Synthesize into 1-2 rich sentences that capture the mood.

Look for these signals in the source:

| Source Location | What It Tells You | |:---|:---| | Root background-color or Tailwind bg-* on layouts | Overall lightness/darkness | | Spacing scale in Tailwind config or CSS vars | Whitespace philosophy | | Number of components vs. wrapper padding | Density | | Custom property naming (--warm-* vs --cool-*) | Color temperature intent | | Comments in theme files | Design intent in the developer's own words |

2. Color Palette & Roles

Extract every unique color from the codebase and assign functional roles. Search across all layers:

Where to find colors:

| Layer | What to Search | |:---|:---| | CSS custom properties | --color-*, --primary, --bg-* | | Tailwind config | theme.extend.colors | | Theme/token files | Color objects, palettes | | Component styles | background-color, color, border-color | | Inline/scoped styles | bg-*, text-* classes in templates | | CSS-in-JS theme objects | colors, palette keys |

How to organize: Group colors by function, not by hue:

  1. Primary Foundation — Background and surface colors
  2. Accent & Interactive — CTA buttons, active states, links
  3. Typography & Text Hierarchy — Primary, secondary, tertiary text
  4. Functional States — Success, error, warning, info

For each color, create a descriptive name that evokes the color's character rather than its raw hex value:

  • ❌ #294056 → "Blue"
  • ✅ #294056 → "Deep Muted Teal-Navy" — Primary CTA, active navigation

Deduplication matters. Codebases often have near-duplicate colors (e.g., #333 and #2C2C2C). Consolidate them under one name that best represents the intended color.

3. Typography Rules

Extract the complete typographic system:

Font families:

  • Check CSS font-family, Tailwind fontFamily, Google Fonts links, or local @font-face declarations.
  • Note the character of each font: geometric vs humanist, serif vs sans, the feeling it evokes.

Type scale (hierarchy):

  • Find every heading level (H1-H6) and body text, noting:
    • font-size (in rem or px)
    • font-weight (numeric value + descriptive name)
    • letter-spacing (and why — elegance? compactness?)
    • line-height (generous for readability? tight for display?)
  • Map component usage: Which heading level do product cards use? What about hero sections?

Spacing principles:

  • How does text spacing relate to the overall spacing scale?
  • Letter-spacing patterns on headings vs body
  • Line-height philosophy (generous/relaxed for body, tighter for display)

4. Component Stylings

Analyze the 4-5 most important UI primitives:

Buttons:

  • Corner radius (and what it communicates — playful? professional? minimal?)
  • Color scheme for primary, secondary, and ghost variants
  • Hover/focus/active states and transition timing
  • Padding ratios (horizontal vs vertical)

Cards / Containers:

  • Corner radius (often different from buttons — slightly rounder)
  • Shadow strategy: flat, subtle hover shadows, or always elevated?
  • Border treatment: hairline borders, colored accents, or none?
  • Internal padding (generous or compact?)
  • Image treatment within cards (full-bleed, padded, rounded?)

Navigation:

  • Layout pattern (horizontal bar, vertical sidebar, drawer)
  • Typography treatment (uppercase, letter-spacing, weight)
  • Active/hover state indicators (underline, color, background)
  • Mobile behavior (hamburger, bottom nav, drawer)

Inputs & Forms:

  • Border style and focus state behavior
  • Corner style consistency with buttons
  • Padding and touch-target sizing

Domain-Specific Components:

  • Identify 1-2 components unique to this project (e.g., product cards, dashboard widgets, chat bubbles) and describe their styling patterns.

5. Layout Principles

Extract the structural system:

Grid & Structure:

  • Max content width (from max-width on containers)
  • Column system (CSS Grid, Flexbox patterns, defined breakpoints)
  • Responsive breakpoints (from media queries or Tailwind config)

Whitespace Strategy:

  • Base spacing unit (8px grid? 4px? custom?)
  • Section margins (how much space between major sections)
  • Edge padding (page margins at different breakpoints)

Alignment & Visual Balance:

  • Text alignment patterns (centered heroes, left-aligned body)
  • Image-to-text ratios
  • Visual weight distribution

Responsive Behavior:

  • Mobile-first or desktop-first?
  • How do grids collapse? Padding scale?
  • Touch target sizing

6. Stitch Generation Notes

Synthesize the extraction into actionable prompts for Stitch:

  • Atmosphere language: Translate the mood into natural descriptors
  • Color references: List colors by descriptive name + hex
  • Component prompts: Write 2-3 example prompts that would recreate key components in Stitch
  • Iteration guidance: Tips for refining screens in this design system

Phase 3: Write the DESIGN.md

Assemble everything into the standard DESIGN.md format. Place it at .stitch/DESIGN.md in the project directory (create the .stitch/ directory if it doesn't exist).

[!IMPORTANT] You MUST include the YAML frontmatter at the top of the file with name and colors mapping, exactly as shown in the example at examples/DESIGN.md. This structured data is required for other skills to parse the design system.

Failure to include this YAML block with at least the core color tokens is a failure to use this skill correctly.

Use the format from the example at examples/DESIGN.md as your template. The file must start with the YAML block, followed by the markdown sections:

# Design System: [Project Name]
**Project ID:** [If known, otherwise omit]

## 1. Visual Theme & Atmosphere
[Rich 2-paragraph description of mood, philosophy, and key characteristics]

## 2. Color Palette & Roles
### Primary Foundation
### Accent & Interactive
### Typography & Text Hierarchy
### Functional States

## 3. Typography Rules
### Hierarchy & Weights
### Spacing Principles

## 4. Component Stylings
### Buttons
### Cards & [Domain-Specific Containers]
### Navigation
### Inputs & Forms
### [Domain-Specific Components]

## 5. Layout Principles
### Grid & Structure
### Whitespace Strategy
### Alignment & Visual Balance
### Responsive Behavior & Touch

## 6. Design System Notes for Stitch Generation
### Language to Use
### Color References
### Component Prompts
### Incremental Iteration

Phase 4:

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars8.4k
CategoryDesign
Updated3mo ago
Forks1.1k

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions