extract-design-system/SKILL.md
Extract the design system (fonts, logos, colors, CSS tokens, favicons, OG assets) from a public website URL into a fresh local git repo with a fact-only README. Use when the user wants to "extract a design system", "steal a design", "pull fonts and colors from a site", "scrape design tokens", "build a design-system repo from a URL", or prepare assets to upload to claude.ai/design.
npx skillsauth add pmatos/skills extract-design-systemInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Turn a public URL into a local git repo full of that site's real design assets and tokens. Only capture what is actually in the page and its linked resources — never invent colors, fonts, or brand facts from visual inspection.
https://....~/design-systems/. Ask; do not assume.example.com → example-com). Offer the default, let the user override.Confirm all three before running anything.
Use WebFetch on the URL and ask it to return: page title, meta description, and any mentions of brand or site name. This is cheap and gives you enough to confirm the target is what the user expects. If WebFetch is blocked, skip to Step 2 without retrying.
mkdir -p "<parent>/<repo-name>"
uv run "${CLAUDE_PLUGIN_ROOT}/extract-design-system/scripts/extract.py" \
"<url>" --output "<parent>/<repo-name>"
${CLAUDE_PLUGIN_ROOT} is set by Claude Code to the plugin's install directory. If it is unset (skill loaded outside a plugin), fall back to the path shown in the skill's own directory — e.g. resolve the script relative to this SKILL.md.
The script uses requests + beautifulsoup4 + tinycss2 to:
@import one level).@font-face rules and download each font file into fonts/.:root / html CSS custom properties into tokens/variables.css.images/favicons/.<svg> blocks (likely logos) into logos/.images/.source/page.html.manifest.json and a fact-only README.md.On success it prints a JSON summary (fonts, stylesheets, favicons, inline SVGs, custom-property counts).
If the summary shows near-zero CSS/fonts/SVGs, the site is likely a JS SPA. Render it with a real browser and re-run with --html:
3a. Playwright CLI (preferred fallback):
playwright install chromium # only if not yet installed
cat > /tmp/render.js <<'EOF'
const { chromium } = require('playwright');
(async () => {
const b = await chromium.launch();
const p = await b.newPage({ userAgent:
'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 Chrome/126.0 Safari/537.36' });
await p.goto(process.argv[2], { waitUntil: 'networkidle', timeout: 60000 });
process.stdout.write(await p.content());
await b.close();
})();
EOF
node /tmp/render.js "<url>" > /tmp/rendered.html
3b. MCP Playwright tools (if Node/Playwright CLI fails): use mcp__plugin_playwright_playwright__browser_navigate, then mcp__plugin_playwright_playwright__browser_evaluate with () => document.documentElement.outerHTML to capture HTML. Write it to /tmp/rendered.html.
3c. claude-in-chrome (last resort): load the tool with ToolSearch select:mcp__claude-in-chrome__navigate,mcp__claude-in-chrome__get_page_text, navigate, then use javascript_tool to read document.documentElement.outerHTML.
Then re-run the extractor with the rendered HTML:
uv run "${CLAUDE_PLUGIN_ROOT}/extract-design-system/scripts/extract.py" \
"<url>" --output "<parent>/<repo-name>" --html /tmp/rendered.html
cd "<parent>/<repo-name>"
git init -q
git add -A
git commit -q -m "Initial extraction from <url>"
Report the repo path, a one-line summary of what was captured, and any obvious gaps (e.g. zero fonts — probably means a JS-rendered site; rerun with Step 3).
og:image, no theme color, no @font-face), leave it out of the README — do not invent.manifest.json and README.md and re-downloads assets.<repo-name>/
├── README.md # fact-only summary
├── manifest.json # structured extraction record
├── fonts/ # downloaded font files
├── logos/ # inline SVGs (candidate logos)
├── images/ # og:image and other page images
│ └── favicons/ # favicons + apple-touch + web-manifest icons
├── css/ # downloaded stylesheets
├── tokens/
│ ├── variables.css # extracted :root custom properties
│ └── fonts.css # rewritten @font-face rules pointing to local files
└── source/
├── page.html # raw/rendered HTML snapshot
└── manifest.webmanifest # if the site exposes one
data-ai
Upscale raster images with a local OpenCV EDSR super-resolution model, then produce an exact target pixel size. Use when the user asks to upscale, enlarge, super-resolve, make a higher-resolution version, or create a wallpaper/print-size raster from an existing image while preserving the original artwork.
tools
This skill should be used when the user asks to "investigate issue", "investigate
development
This skill should be used when the user asks "what's going on", "wigo", "status", "where was I", "what were we doing", "catch me up", "tree status", "branch status", or wants a comprehensive situational briefing on the current git tree, session history, and associated PR. Also triggered by the /wigo command.
development
This skill should be used when the user asks to "plan this", "make a plan", "create an implementation plan", "how should I implement", "design the implementation", "plan the refactor", "plan the migration", "plan the feature", "break this down into steps", "implementation strategy", "deep plan", "thorough plan", or wants a thorough, multi-phase implementation plan with codebase exploration before writing any code.