stitch::extract-design-md

Extract a Stitch-compatible DESIGN.md from frontend source code.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/vikingokft/vikingo-studio-skills --skill stitch-extract-design-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch::extract-design-md
Source: https://github.com/vikingokft/vikingo-studio-skills/tree/main/design/extract-design-md
Command: npx skills add https://github.com/vikingokft/vikingo-studio-skills --skill stitch-extract-design-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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 you want 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 you just say "what does this app look like?" or "pull out the design from this code."

Core Features & Use Cases

  • Read frontend source to generate DESIGN.md containing colors, typography, spacing, component patterns, and tokens
  • Supports React, Vue, Svelte, Angular, and plain HTML/CSS projects
  • Use cases include design-system reconstruction, visual-audit, token extraction, and pattern analysis

Quick Start

To begin, run the design-extraction workflow on your frontend repository to generate DESIGN.md.

Frequently Asked Questions about stitch::extract-design-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract design tokens from frontend source code?

To extract design tokens from frontend source code, analyze component files, stylesheets, Tailwind configs, and theme definitions to generate a comprehensive DESIGN.md document capturing colors, typography, spacing, and tokens.

Can I reverse-engineer a design system from an existing React or Vue codebase?

Yes, you can reverse-engineer a design system from React, Vue, Svelte, Angular, or plain HTML/CSS codebases by analyzing frontend artifacts and extracting visual patterns into a Stitch-compatible design system document.

What is a visual audit of a frontend project and when do I need it?

A visual audit of a frontend project involves analyzing styling patterns and component files to understand the visual language, useful when reconstructing a design system or auditing inconsistent UI components across a repository.

Does the design extraction process work with Tailwind configs and plain HTML/CSS?

Yes, the design extraction process works with Tailwind configs, plain HTML/CSS, and various web frameworks by reading theme definitions and stylesheets to pull design tokens and styling patterns into a structured document.

What's the best way to generate a design system doc from multiple framework source files?

The best way to generate a design system doc from multiple framework source files is to run a design-extraction workflow that reads component files, stylesheets, and token files across React, Vue, Svelte, or Angular to produce a unified DESIGN.md.

What are the limitations of extracting design tokens from source code?

Limitations of extracting design tokens from source code include relying on the presence of structured frontend artifacts like stylesheets, theme definitions, and token files, meaning dynamic styles applied at runtime may not be fully captured.