[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F50GZ5F22TYDDFKFJPNBWR":3,"skill-same:01M7F50GZ5F22TYDDFKFJPNBWR":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7F50GZ5F22TYDDFKFJPNBWR","stitch::extract-design-md",null,"Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML\u002FCSS, 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.\"","26BB\u002Fagent-fleet-os","26BB","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113676969?v=4","01M7F3AVX9MTTAHCYTANRGEE52","Bhushan Vijay Bhosale","01M7F3AVY15DJBX1CE4H25P52T",0,"MIT","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: stitch::extract-design-md\ndescription: >-\n  Extract a comprehensive design system (DESIGN.md) directly from frontend source\n  code — React, Vue, Svelte, Angular, plain HTML\u002FCSS, or any web framework. Analyzes\n  component files, stylesheets, Tailwind configs, theme definitions, and design tokens\n  to produce a rich, Stitch-compatible design system document. Use this skill whenever\n  the user wants to reverse-engineer a design system from an existing codebase, audit\n  the visual language of a project, extract design tokens from source files, or\n  understand the styling patterns in a frontend repo — even if they just say \"what\n  does this app look like?\" or \"pull out the design from this code.\"\nallowed-tools:\n  - \"stitch*:*\"\n  - \"Bash\"\n  - \"Read\"\n  - \"Write\"\n  - \"web_fetch\"\n---\n\n# Extract Design System from Frontend Code\n\nAnalyze frontend source code to extract a comprehensive design system document\n(DESIGN.md) that captures the project's visual language — colors, typography,\nspacing, component patterns, and layout principles — directly from the source\nfiles, without needing to build or render the application.\n\n## Why This Exists\n\nThe `design-md` skill works from rendered HTML. But often you have a codebase\nand want to understand its design system before you can even run the app —\nmaybe dependencies are missing, the build is broken, or you just want a quick\naudit. This skill reads the source files themselves: stylesheets, component\nfiles, theme configs, and Tailwind setups. It's faster and works anywhere.\n\n## When to Use\n\n- User has a frontend codebase and wants to extract or document its design system\n- User wants to migrate a project's visual identity into Stitch\n- User asks to \"audit the styling\" or \"understand the design language\" of a repo\n- User wants to create a DESIGN.md from existing source code\n- The app can't be built\u002Frendered but the source is available\n- User wants to unify or reconcile inconsistent styles across a codebase\n\n## Prerequisites\n\n- Access to the frontend project's source directory\n- No build or runtime dependencies needed — this skill reads source files only\n\n---\n\n## Workflow\n\n### Phase 1: Project Discovery\n\nStart by understanding what you're working with. This determines which\nextraction patterns to use.\n\n#### 1. Detect the Framework and Stack\n\nScan the project root for telltale files:\n\n| Signal File | Framework \u002F Tool |\n|:---|:---|\n| `package.json` with `react` | React \u002F Next.js |\n| `package.json` with `vue` | Vue \u002F Nuxt |\n| `package.json` with `svelte` | Svelte \u002F SvelteKit |\n| `package.json` with `@angular\u002Fcore` | Angular |\n| `tailwind.config.js\u002Fts` | Tailwind CSS |\n| `postcss.config.js` | PostCSS pipeline |\n| `styled-components` or `@emotion` in deps | CSS-in-JS |\n| `.css` \u002F `.scss` \u002F `.less` files only | Plain CSS \u002F SASS |\n| `theme.js` \u002F `theme.ts` \u002F `tokens.js` | Design token files |\n\nRead `package.json` first — it reveals the framework, CSS tooling, and any\ndesign-token libraries (e.g., `style-dictionary`, `@chakra-ui\u002Freact`,\n`@mui\u002Fmaterial`, `ant-design`). This context tells you *where* to look for\nstyling information.\n\n#### 2. Map the Source Tree\n\nIdentify the key directories and files you'll analyze:\n\n```\nsrc\u002F\n├── components\u002F     ← Component-level styles\n├── styles\u002F         ← Global stylesheets\n├── theme\u002F          ← Theme definitions, tokens\n├── assets\u002F         ← Fonts, images\n├── app.css         ← Root styles\n└── index.css       ← Entry CSS\n```\n\nAlso check for:\n- `tailwind.config.js` \u002F `tailwind.config.ts` — Custom colors, fonts, spacing\n- `globals.css` \u002F `global.css` — CSS custom properties (variables)\n- Any `theme.*` or `tokens.*` files\n- Component library config (e.g., `chakra-theme.ts`, `vuetify.config.ts`)\n\n#### 3. Read Framework-Specific Guidance\n\nConsult the appropriate reference for extraction patterns:\n\n- **React \u002F Next.js \u002F Tailwind** → [references\u002Freact-tailwind.md](references\u002Freact-tailwind.md)\n- **Vue \u002F Nuxt** → [references\u002Fvue.md](references\u002Fvue.md)\n- **Svelte \u002F SvelteKit** → [references\u002Fsvelte.md](references\u002Fsvelte.md)\n- **Angular** → [references\u002Fangular.md](references\u002Fangular.md)\n- **Plain CSS \u002F SASS \u002F Less** → [references\u002Fplain-css.md](references\u002Fplain-css.md)\n\nThese references contain framework-specific patterns for locating colors,\ntypography, spacing, and component styles. Read the one that matches before\nproceeding.\n\n---\n\n### Phase 2: Deep Extraction\n\nWork through each design dimension systematically. For each one, gather raw\ndata from the source files, then synthesize it into descriptive language.\n\nThe goal isn't to dump every CSS property — it's to understand the *intent*\nbehind the styling choices and describe them in human, editorial language that\nanother designer (or Stitch) can use to recreate the same visual feel.\n\n#### 1. Visual Theme & Atmosphere\n\nRead the broadest styling first to understand the overall mood:\n\n- **Root background**: What's the `body` or root element background? Light\n  cream (#f-range) signals airy\u002Fclean; dark (#0-#2 range) signals moody\u002Fdramatic.\n- **Whitespace philosophy**: Are spacing values generous (32px+) or tight?\n  Check padding\u002Fmargin values on root containers, section wrappers, and card components.\n- **Density**: Count the components per page\u002Fsection. Few with space = minimal;\n  many packed tight = information-dense.\n- **Color temperature**: Are the neutrals warm (creams, tans) or cool (blue-grays, slates)?\n- **Overall feel**: Synthesize into 1-2 rich sentences that capture the mood.\n\nLook for these signals in the source:\n\n| Source Location | What It Tells You |\n|:---|:---|\n| Root `background-color` or Tailwind `bg-*` on layouts | Overall lightness\u002Fdarkness |\n| Spacing scale in Tailwind config or CSS vars | Whitespace philosophy |\n| Number of components vs. wrapper padding | Density |\n| Custom property naming (`--warm-*` vs `--cool-*`) | Color temperature intent |\n| Comments in theme files | Design intent in the developer's own words |\n\n#### 2. Color Palette & Roles\n\nExtract every unique color from the codebase and assign functional roles.\nSearch across all layers:\n\n**Where to find colors:**\n\n| Layer | What to Search |\n|:---|:---|\n| CSS custom properties | `--color-*`, `--primary`, `--bg-*` |\n| Tailwind config | `theme.extend.colors` |\n| Theme\u002Ftoken files | Color objects, palettes |\n| Component styles | `background-color`, `color`, `border-color` |\n| Inline\u002Fscoped styles | `bg-*`, `text-*` classes in templates |\n| CSS-in-JS theme objects | `colors`, `palette` keys |\n\n**How to organize:** Group colors by function, not by hue:\n\n1. **Primary Foundation** — Background and surface colors\n2. **Accent & Interactive** — CTA buttons, active states, links\n3. **Typography & Text Hierarchy** — Primary, secondary, tertiary text\n4. **Functional States** — Success, error, warning, info\n\nFor each color, create a descriptive name that evokes the color's character\nrather than its raw hex value:\n\n- ❌ `#294056` → \"Blue\"\n- ✅ `#294056` → **\"Deep Muted Teal-Navy\"** — Primary CTA, active navigation\n\n**Deduplication matters.** Codebases often have near-duplicate colors (e.g.,\n`#333` and `#2C2C2C`). Consolidate them under one name that best represents\nthe intended color.\n\n#### 3. Typography Rules\n\nExtract the complete typographic system:\n\n**Font families:**\n- Check CSS `font-family`, Tailwind `fontFamily`, Google Fonts links, or\n  local `@font-face` declarations.\n- Note the **character** of each font: geometric vs humanist, serif vs sans,\n  the feeling it evokes.\n\n**Type scale (hierarchy):**\n- Find every heading level (H1-H6) and body text, noting:\n  - `font-size` (in rem or px)\n  - `font-weight` (numeric value + descriptive name)\n  - `letter-spacing` (and why — elegance? compactness?)\n  - `line-height` (generous for readability? tight for display?)\n- Map component usage: Which heading level do product cards use? What about\n  hero sections?\n\n**Spacing principles:**\n- How does text spacing relate to the overall spacing scale?\n- Letter-spacing patterns on headings vs body\n- Line-height philosophy (generous\u002Frelaxed for body, tighter for display)\n\n#### 4. Component Stylings\n\nAnalyze the 4-5 most important UI primitives:\n\n**Buttons:**\n- Corner radius (and what it communicates — playful? professional? minimal?)\n- Color scheme for primary, secondary, and ghost variants\n- Hover\u002Ffocus\u002Factive states and transition timing\n- Padding ratios (horizontal vs vertical)\n\n**Cards \u002F Containers:**\n- Corner radius (often different from buttons — slightly rounder)\n- Shadow strategy: flat, subtle hover shadows, or always elevated?\n- Border treatment: hairline borders, colored accents, or none?\n- Internal padding (generous or compact?)\n- Image treatment within cards (full-bleed, padded, rounded?)\n\n**Navigation:**\n- Layout pattern (horizontal bar, vertical sidebar, drawer)\n- Typography treatment (uppercase, letter-spacing, weight)\n- Active\u002Fhover state indicators (underline, color, background)\n- Mobile behavior (hamburger, bottom nav, drawer)\n\n**Inputs & Forms:**\n- Border style and focus state behavior\n- Corner style consistency with buttons\n- Padding and touch-target sizing\n\n**Domain-Specific Components:**\n- Identify 1-2 components unique to this project (e.g., product cards,\n  dashboard widgets, chat bubbles) and describe their styling patterns.\n\n#### 5. Layout Principles\n\nExtract the structural system:\n\n**Grid & Structure:**\n- Max content width (from `max-width` on containers)\n- Column system (CSS Grid, Flexbox patterns, defined breakpoints)\n- Responsive breakpoints (from media queries or Tailwind config)\n\n**Whitespace Strategy:**\n- Base spacing unit (8px grid? 4px? custom?)\n- Section margins (how much space between major sections)\n- Edge padding (page margins at different breakpoints)\n\n**Alignment & Visual Balance:**\n- Text alignment patterns (centered heroes, left-aligned body)\n- Image-to-text ratios\n- Visual weight distribution\n\n**Responsive Behavior:**\n- Mobile-first or desktop-first?\n- How do grids collapse? Padding scale?\n- Touch target sizing\n\n#### 6. Stitch Generation Notes\n\nSynthesize the extraction into actionable prompts for Stitch:\n\n- **Atmosphere language**: Translate the mood into natural descriptors\n- **Color references**: List colors by descriptive name + hex\n- **Component prompts**: Write 2-3 example prompts that would recreate\n  key components in Stitch\n- **Iteration guidance**: Tips for refining screens in this design system\n\n---\n\n### Phase 3: Write the DESIGN.md\n\nAssemble everything into the standard DESIGN.md format. Place it at\n`.stitch\u002FDESIGN.md` in the project directory (create the `.stitch\u002F` directory\nif it doesn't exist).\n\n> [!IMPORTANT]\n> 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\u002FDESIGN.md](examples\u002FDESIGN.md). This structured data is required for other skills to parse the design system.\n>\n> Failure to include this YAML block with at least the core color tokens is a failure to use this skill correctly.\n\nUse the format from the example at [examples\u002FDESIGN.md](examples\u002FDESIGN.md) as your template. The file must start with the YAML block, followed by the markdown sections:\n\n```markdown\n# Design System: [Project Name]\n**Project ID:** [If known, otherwise omit]\n\n## 1. Visual Theme & Atmosphere\n[Rich 2-paragraph description of mood, philosophy, and key characteristics]\n\n## 2. Color Palette & Roles\n### Primary Foundation\n### Accent & Interactive\n### Typography & Text Hierarchy\n### Functional States\n\n## 3. Typography Rules\n### Hierarchy & Weights\n### Spacing Principles\n\n## 4. Component Stylings\n### Buttons\n### Cards & [Domain-Specific Containers]\n### Navigation\n### Inputs & Forms\n### [Domain-Specific Components]\n\n## 5. Layout Principles\n### Grid & Structure\n### Whitespace Strategy\n### Alignment & Visual Balance\n### Responsive Behavior & Touch\n\n## 6. Design System Notes for Stitch Generation\n### Language to Use\n### Color References\n### Component Prompts\n### Incremental Iteration\n```\n\n---\n\n### Phase 4: Integration (Optional)\n\nIf the user wants to push the design system into Stitch:\n\n1. Hand off to the `manage-design-system` skill for the MCP create\u002Fupdate calls\n2. The DESIGN.md you wrote is the input — the manage-design-system skill handles\n   the Stitch API integration\n\nIf the user just wants the document, you're done after Phase 3.\n\n---\n\n## Quality Checklist\n\nBefore delivering the DESIGN.md, verify:\n\n- [ ] Every color has a descriptive name, hex code, and functional role\n- [ ] Typography includes font family, character description, and full hierarchy\n- [ ] Component styles describe shape, color, states, and transitions\n- [ ] Layout includes max-width, grid, breakpoints, and spacing strategy\n- [ ] Stitch generation notes use natural language, not CSS syntax\n- [ ] The atmosphere section reads like editorial copy, not technical docs\n- [ ] Near-duplicate colors are consolidated\n- [ ] The document captures the *intent* behind styling, not just raw values\n\n## Tips for Better Extraction\n\n- **Read comments and commit messages.** Developers often document design\n  intent in code comments (`\u002F* hero section — breathable *\u002F`) and commit\n  messages. These are gold for understanding the *why*.\n- **Check for design-token libraries.** If the project uses `style-dictionary`,\n  `@tokens-studio`, or similar, these files are the most authoritative\n  source of design values.\n- **Theme files are higher-signal than component styles.** A `theme.ts` that\n  defines a palette tells you the intended design system; scattered inline\n  styles in components tell you what actually shipped. Both matter, but\n  start from the theme.\n- **Tailwind config is a design system.** If a project has a customized\n  `tailwind.config.js`, that *is* the design system — extract from it first,\n  then spot-check components for overrides.\n- **CSS custom properties are intentional.** If a developer defined\n  `--brand-primary`, they're telling you this is a design token. Respect that.\n","# Extract Design System from Frontend Code\n\nAnalyze frontend source code to extract a comprehensive design system document\n(DESIGN.md) that captures the project's visual language — colors, typography,\nspacing, component patterns, and layout principles — directly from the source\nfiles, without needing to build or render the application.\n\n## Why This Exists\n\nThe `design-md` skill works from rendered HTML. But often you have a codebase\nand want to understand its design system before you can even run the app —\nmaybe dependencies are missing, the build is broken, or you just want a quick\naudit. This skill reads the source files themselves: stylesheets, component\nfiles, theme configs, and Tailwind setups. It's faster and works anywhere.\n\n## When to Use\n\n- User has a frontend codebase and wants to extract or document its design system\n- User wants to migrate a project's visual identity into Stitch\n- User asks to \"audit the styling\" or \"understand the design language\" of a repo\n- User wants to create a DESIGN.md from existing source code\n- The app can't be built\u002Frendered but the source is available\n- User wants to unify or reconcile inconsistent styles across a codebase\n\n## Prerequisites\n\n- Access to the frontend project's source directory\n- No build or runtime dependencies needed — this skill reads source files only\n\n---\n\n## Workflow\n\n### Phase 1: Project Discovery\n\nStart by understanding what you're working with. This determines which\nextraction patterns to use.\n\n#### 1. Detect the Framework and Stack\n\nScan the project root for telltale files:\n\n| Signal File | Framework \u002F Tool |\n|:---|:---|\n| `package.json` with `react` | React \u002F Next.js |\n| `package.json` with `vue` | Vue \u002F Nuxt |\n| `package.json` with `svelte` | Svelte \u002F SvelteKit |\n| `package.json` with `@angular\u002Fcore` | Angular |\n| `tailwind.config.js\u002Fts` | Tailwind CSS |\n| `postcss.config.js` | PostCSS pipeline |\n| `styled-components` or `@emotion` in deps | CSS-in-JS |\n| `.css` \u002F `.scss` \u002F `.less` files only | Plain CSS \u002F SASS |\n| `theme.js` \u002F `theme.ts` \u002F `tokens.js` | Design token files |\n\nRead `package.json` first — it reveals the framework, CSS tooling, and any\ndesign-token libraries (e.g., `style-dictionary`, `@chakra-ui\u002Freact`,\n`@mui\u002Fmaterial`, `ant-design`). This context tells you *where* to look for\nstyling information.\n\n#### 2. Map the Source Tree\n\nIdentify the key directories and files you'll analyze:\n\n```\nsrc\u002F\n├── components\u002F     ← Component-level styles\n├── styles\u002F         ← Global stylesheets\n├── theme\u002F          ← Theme definitions, tokens\n├── assets\u002F         ← Fonts, images\n├── app.css         ← Root styles\n└── index.css       ← Entry CSS\n```\n\nAlso check for:\n- `tailwind.config.js` \u002F `tailwind.config.ts` — Custom colors, fonts, spacing\n- `globals.css` \u002F `global.css` — CSS custom properties (variables)\n- Any `theme.*` or `tokens.*` files\n- Component library config (e.g., `chakra-theme.ts`, `vuetify.config.ts`)\n\n#### 3. Read Framework-Specific Guidance\n\nConsult the appropriate reference for extraction patterns:\n\n- **React \u002F Next.js \u002F Tailwind** → [references\u002Freact-tailwind.md](references\u002Freact-tailwind.md)\n- **Vue \u002F Nuxt** → [references\u002Fvue.md](references\u002Fvue.md)\n- **Svelte \u002F SvelteKit** → [references\u002Fsvelte.md](references\u002Fsvelte.md)\n- **Angular** → [references\u002Fangular.md](references\u002Fangular.md)\n- **Plain CSS \u002F SASS \u002F Less** → [references\u002Fplain-css.md](references\u002Fplain-css.md)\n\nThese references contain framework-specific patterns for locating colors,\ntypography, spacing, and component styles. Read the one that matches before\nproceeding.\n\n---\n\n### Phase 2: Deep Extraction\n\nWork through each design dimension systematically. For each one, gather raw\ndata from the source files, then synthesize it into descriptive language.\n\nThe goal isn't to dump every CSS property — it's to understand the *intent*\nbehind the styling choices and describe them in human, editorial language that\nanother designer (or Stitch) can use to recreate the same visual feel.\n\n#### 1. Visual Theme & Atmosphere\n\nRead the broadest styling first to understand the overall mood:\n\n- **Root background**: What's the `body` or root element background? Light\n  cream (#f-range) signals airy\u002Fclean; dark (#0-#2 range) signals moody\u002Fdramatic.\n- **Whitespace philosophy**: Are spacing values generous (32px+) or tight?\n  Check padding\u002Fmargin values on root containers, section wrappers, and card components.\n- **Density**: Count the components per page\u002Fsection. Few with space = minimal;\n  many packed tight = information-dense.\n- **Color temperature**: Are the neutrals warm (creams, tans) or cool (blue-grays, slates)?\n- **Overall feel**: Synthesize into 1-2 rich sentences that capture the mood.\n\nLook for these signals in the source:\n\n| Source Location | What It Tells You |\n|:---|:---|\n| Root `background-color` or Tailwind `bg-*` on layouts | Overall lightness\u002Fdarkness |\n| Spacing scale in Tailwind config or CSS vars | Whitespace philosophy |\n| Number of components vs. wrapper padding | Density |\n| Custom property naming (`--warm-*` vs `--cool-*`) | Color temperature intent |\n| Comments in theme files | Design intent in the developer's own words |\n\n#### 2. Color Palette & Roles\n\nExtract every unique color from the codebase and assign functional roles.\nSearch across all layers:\n\n**Where to find colors:**\n\n| Layer | What to Search |\n|:---|:---|\n| CSS custom properties | `--color-*`, `--primary`, `--bg-*` |\n| Tailwind config | `theme.extend.colors` |\n| Theme\u002Ftoken files | Color objects, palettes |\n| Component styles | `background-color`, `color`, `border-color` |\n| Inline\u002Fscoped styles | `bg-*`, `text-*` classes in templates |\n| CSS-in-JS theme objects | `colors`, `palette` keys |\n\n**How to organize:** Group colors by function, not by hue:\n\n1. **Primary Foundation** — Background and surface colors\n2. **Accent & Interactive** — CTA buttons, active states, links\n3. **Typography & Text Hierarchy** — Primary, secondary, tertiary text\n4. **Functional States** — Success, error, warning, info\n\nFor each color, create a descriptive name that evokes the color's character\nrather than its raw hex value:\n\n- ❌ `#294056` → \"Blue\"\n- ✅ `#294056` → **\"Deep Muted Teal-Navy\"** — Primary CTA, active navigation\n\n**Deduplication matters.** Codebases often have near-duplicate colors (e.g.,\n`#333` and `#2C2C2C`). Consolidate them under one name that best represents\nthe intended color.\n\n#### 3. Typography Rules\n\nExtract the complete typographic system:\n\n**Font families:**\n- Check CSS `font-family`, Tailwind `fontFamily`, Google Fonts links, or\n  local `@font-face` declarations.\n- Note the **character** of each font: geometric vs humanist, serif vs sans,\n  the feeling it evokes.\n\n**Type scale (hierarchy):**\n- Find every heading level (H1-H6) and body text, noting:\n  - `font-size` (in rem or px)\n  - `font-weight` (numeric value + descriptive name)\n  - `letter-spacing` (and why — elegance? compactness?)\n  - `line-height` (generous for readability? tight for display?)\n- Map component usage: Which heading level do product cards use? What about\n  hero sections?\n\n**Spacing principles:**\n- How does text spacing relate to the overall spacing scale?\n- Letter-spacing patterns on headings vs body\n- Line-height philosophy (generous\u002Frelaxed for body, tighter for display)\n\n#### 4. Component Stylings\n\nAnalyze the 4-5 most important UI primitives:\n\n**Buttons:**\n- Corner radius (and what it communicates — playful? professional? minimal?)\n- Color scheme for primary, secondary, and ghost variants\n- Hover\u002Ffocus\u002Factive states and transition timing\n- Padding ratios (horizontal vs vertical)\n\n**Cards \u002F Containers:**\n- Corner radius (often different from buttons — slightly rounder)\n- Shadow strategy: flat, subtle hover shadows, or always elevated?\n- Border treatment: hairline borders, colored accents, or none?\n- Internal padding (generous or compact?)\n- Image treatment within cards (full-bleed, padded, rounded?)\n\n**Navigation:**\n- Layout pattern (horizontal bar, vertical sidebar, drawer)\n- Typography treatment (uppercase, letter-spacing, weight)\n- Active\u002Fhover state indicators (underline, color, background)\n- Mobile behavior (hamburger, bottom nav, drawer)\n\n**Inputs & Forms:**\n- Border style and focus state behavior\n- Corner style consistency with buttons\n- Padding and touch-target sizing\n\n**Domain-Specific Components:**\n- Identify 1-2 components unique to this project (e.g., product cards,\n  dashboard widgets, chat bubbles) and describe their styling patterns.\n\n#### 5. Layout Principles\n\nExtract the structural system:\n\n**Grid & Structure:**\n- Max content width (from `max-width` on containers)\n- Column system (CSS Grid, Flexbox patterns, defined breakpoints)\n- Responsive breakpoints (from media queries or Tailwind config)\n\n**Whitespace Strategy:**\n- Base spacing unit (8px grid? 4px? custom?)\n- Section margins (how much space between major sections)\n- Edge padding (page margins at different breakpoints)\n\n**Alignment & Visual Balance:**\n- Text alignment patterns (centered heroes, left-aligned body)\n- Image-to-text ratios\n- Visual weight distribution\n\n**Responsive Behavior:**\n- Mobile-first or desktop-first?\n- How do grids collapse? Padding scale?\n- Touch target sizing\n\n#### 6. Stitch Generation Notes\n\nSynthesize the extraction into actionable prompts for Stitch:\n\n- **Atmosphere language**: Translate the mood into natural descriptors\n- **Color references**: List colors by descriptive name + hex\n- **Component prompts**: Write 2-3 example prompts that would recreate\n  key components in Stitch\n- **Iteration guidance**: Tips for refining screens in this design system\n\n---\n\n### Phase 3: Write the DESIGN.md\n\nAssemble everything into the standard DESIGN.md format. Place it at\n`.stitch\u002FDESIGN.md` in the project directory (create the `.stitch\u002F` directory\nif it doesn't exist).\n\n> [!IMPORTANT]\n> 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\u002FDESIGN.md](examples\u002FDESIGN.md). This structured data is required for other skills to parse the design system.\n>\n> Failure to include this YAML block with at least the core color tokens is a failure to use this skill correctly.\n\nUse the format from the example at [examples\u002FDESIGN.md](examples\u002FDESIGN.md) as your template. The file must start with the YAML block, followed by the markdown sections:\n\n```markdown\n# Design System: [Project Name]\n**Project ID:** [If known, otherwise omit]\n\n## 1. Visual Theme & Atmosphere\n[Rich 2-paragraph description of mood, philosophy, and key characteristics]\n\n## 2. Color Palette & Roles\n### Primary Foundation\n### Accent & Interactive\n### Typography & Text Hierarchy\n### Functional States\n\n## 3. Typography Rules\n### Hierarchy & Weights\n### Spacing Principles\n\n## 4. Component Stylings\n### Buttons\n### Cards & [Domain-Specific Containers]\n### Navigation\n### Inputs & Forms\n### [Domain-Specific Components]\n\n## 5. Layout Principles\n### Grid & Structure\n### Whitespace Strategy\n### Alignment & Visual Balance\n### Responsive Behavior & Touch\n\n## 6. Design System Notes for Stitch Generation\n### Language to Use\n### Color References\n### Component Prompts\n### Incremental Iteration\n```\n\n---\n\n### Phase 4: Integration (Optional)\n\nIf the user wants to push the design system into Stitch:\n\n1. Hand off to the `manage-design-system` skill for the MCP create\u002Fupdate calls\n2. The DESIGN.md you wrote is the input — the manage-design-system skill handles\n   the Stitch API integration\n\nIf the user just wants the document, you're done after Phase 3.\n\n---\n\n## Quality Checklist\n\nBefore delivering the DESIGN.md, verify:\n\n- [ ] Every color has a descriptive name, hex code, and functional role\n- [ ] Typography includes font family, character description, and full hierarchy\n- [ ] Component styles describe shape, color, states, and transitions\n- [ ] Layout includes max-width, grid, breakpoints, and spacing strategy\n- [ ] Stitch generation notes use natural language, not CSS syntax\n- [ ] The atmosphere section reads like editorial copy, not technical docs\n- [ ] Near-duplicate colors are consolidated\n- [ ] The document captures the *intent* behind styling, not just raw values\n\n## Tips for Better Extraction\n\n- **Read comments and commit messages.** Developers often document design\n  intent in code comments (`\u002F* hero section — breathable *\u002F`) and commit\n  messages. These are gold for understanding the *why*.\n- **Check for design-token libraries.** If the project uses `style-dictionary`,\n  `@tokens-studio`, or similar, these files are the most authoritative\n  source of design values.\n- **Theme files are higher-signal than component styles.** A `theme.ts` that\n  defines a palette tells you the intended design system; scattered inline\n  styles in components tell you what actually shipped. Both matter, but\n  start from the theme.\n- **Tailwind config is a design system.** If a project has a customized\n  `tailwind.config.js`, that *is* the design system — extract from it first,\n  then spot-check components for overrides.\n- **CSS custom properties are intentional.** If a developer defined\n  `--brand-primary`, they're telling you this is a design token. Respect that.\n",{"name":5,"description":7,"allowed-tools":24},[25,26,27,28,29],"stitch*:*","Bash","Read","Write","web_fetch","main","98985c16dc8df1bbd7dcd1bc698cd997a093e751","stitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os","https:\u002F\u002Fgithub.com\u002F26BB","🚀 Aspiring Product Manager | CS @ GS Moze\r\n\r\n🛠️ Building 0→1 products across SaaS & clean-tech\r\n\r\n📊 Turning user feedback & data into shipped features","2026-11-05 13:34:38",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add 26BB\u002Fagent-fleet-os --skill \"stitch::extract-design-md\"",{"tool":43,"command":44},"bunx","bunx skills add 26BB\u002Fagent-fleet-os --skill \"stitch::extract-design-md\"",{"tool":46,"command":47},"pnpm","pnpm dlx skills add 26BB\u002Fagent-fleet-os --skill \"stitch::extract-design-md\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002FSKILL.md",true,[51,57,61,65,69,73],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"examples\u002FDESIGN.md","REFERENCE","参考文档",6960,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002Fexamples\u002FDESIGN.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fangular.md",5237,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002Freferences\u002Fangular.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fplain-css.md",3991,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002Freferences\u002Fplain-css.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Freact-tailwind.md",4583,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002Freferences\u002Freact-tailwind.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fsvelte.md",2714,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002Freferences\u002Fsvelte.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvue.md",3077,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fextract-design-md\u002Freferences\u002Fvue.md",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F51NQSCRM2PWFMATCV9MEG","taste-design","Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F51JGTS9VJ3S9T6VMQWZ08","stitch-loop","Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fstitch-loop\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F51EZR2XYDWMA3XKWH1HX2","site-md","Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fsite-md\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7F51BNCMP0GQ7SGP39SZYDP","enhance-prompt","Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI\u002FUX keywords, injects design system context, and structures output for better generation results.","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fenhance-prompt\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7F518SX707EB3X42B2V7HRA","design-md","Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fdesign-md\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7F5148PVYTA76NR3X0YK8SK","stitch::upload-to-stitch","Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fupload-to-stitch\u002FSKILL.md",[],[]]