extract-design-system
Catalogue stub — full skill: arvindrk/extract-design-system
Decision tree
-
Is the full skill already installed?
- Global:
f=~/.agents/skills/extract-design-system/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" - Project:
f=.agents/skills/extract-design-system/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" installed→ the skill is installed asextract-design-system, invoke it and proceedpointer→ go to step 2
- Global:
-
Detect scope, then install:
bash[ -e ~/.agents/skills/extract-design-system ] && echo "global" || echo "project"Global:
bashnpx skills add arvindrk/extract-design-system --skill extract-design-system -g -yProject:
bashnpx skills add arvindrk/extract-design-system --skill extract-design-system -yClaude Code: send a command as a chat message starting with
!to run it without leaving the conversation.
Heads-up
- Requires: Node.js with npx and network access (at use time the skill runs
npx playwright install chromiumand theextract-design-systemnpm package) - License: MIT
Invoke after install
- Skill name:
extract-design-system - Triggers: "extract design system", "reverse-engineer tokens", "extract tokens from website"
What it does
Reverse-engineers starter design tokens from a public website URL. The skill has the agent run the extract-design-system CLI (a headless Chromium crawl) and then summarise what it found: likely primary, secondary and accent colors, detected fonts, and the spacing, radius and shadow scales. It writes .extract-design-system/raw.json and normalized.json, plus a W3C-style design-system/tokens.json and a design-system/tokens.css of CSS custom properties. It extracts tokens and starter assets, not a component library, and it asks before changing any existing app code or styles. Results are good for initialising a project, not pixel-perfect reproduction.
When NOT to use
- Figma-source token extraction → use the Figma MCP (
figma-official-skills) orfigma-variables-tokens-generator - A DESIGN.md spec document rather than token files → use
extract-design-md - Building a token architecture from scratch → use
design-tokens-skill


