design-system-extract

Extract design tokens from source code, brand guides, and screenshots into structured token files.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill design-system-extract-mjlike123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-extract
Source: https://github.com/Mjlike123/ui-prototype-workbench/tree/main/.agents/skills/monkren-design/skills/_deprecated/design-system-extract
Command: npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill design-system-extract-mjlike123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting design work that must match an existing visual language, manually hunting down colors, fonts, spacing, and shadow values across codebases and brand documents is slow and error-prone. This Skill extracts those design tokens directly from the source and outputs a structured token file so subsequent designs stay consistent. ## Core Features & Use Cases - Multi-source token extraction: Reads theme files (theme.ts, tokens.css, _variables.scss, tailwind.config.js), brand guidelines, live sites, or screenshots to capture real values without guessing. - Categorized token coverage: Extracts colors (brand, semantic, neutrals, surfaces), typography (families, sizes, weights, line heights), spacing scales, border radii, shadows, and optional tokens like z-index, animation, and breakpoints. - Structured output and findings report: Generates a tokens.css (or tokens.ts/tokens.json/Tailwind config) file plus a summary of gaps, inconsistencies, and recommended next steps. - Use Case: Point it at an existing codebase and receive a complete tokens.css with documented inconsistencies such as near-duplicate blues or mismatched neutral grays. ## Quick Start Ask the AI to extract design tokens from your project's theme files and generate a tokens.css file with a findings report. Note: This Skill is deprecated as of v5.0; the maintainers recommend Style Dictionary or Figma Variables exports for token extraction going forward.

Frequently Asked Questions about design-system-extract

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

FAQPage Schema
How do I extract design tokens from an existing codebase?

Point the extraction workflow at your theme files such as theme.ts, tokens.css, _variables.scss, or tailwind.config.js. It scans colors, typography, spacing, radii, and shadows, then generates a structured tokens.css or equivalent file with a findings report.

What design token categories can be extracted from source files?

The extraction covers brand and semantic colors, neutral scales, surface colors, font families with fallback stacks, type sizes and weights, line heights, spacing scales, border radii, elevation shadows, and optionally z-index, animation, and breakpoint tokens.

Can design tokens be extracted from screenshots or brand guidelines?

Yes, the workflow accepts brand guidelines in PDF or Figma form, live sites, and screenshots in addition to codebases. If the source is ambiguous, it asks for clarification rather than inventing token values.

What output formats does design token extraction produce?

It writes a tokens.css file by default, or matches the source format and naming conventions, producing tokens.ts with typed exports, tokens.json, or a Tailwind config extension. Tokens are grouped by category with clear names.

Is the design-system-extract skill still maintained?

No, it was marked deprecated in v5.0 and will be physically deleted after six months without usage. The maintainers recommend Style Dictionary or Figma Variables exports for token extraction instead.