agentleFS
Sign inStart free
Dweeb1578Dweeb1578/claude-grounding-skills/skills/design-extractor/SKILL.md

design-extractor

Skill0 starsChanged 5 months agoMITView on GitHub

Use when building or improving any UI, when asked to replicate or match a website's look or fonts, or when the user references a specific site's design ("make it look like X", "match the design of Y", "what fonts/colors does Z use"). Renders the live site in a real browser and extracts its design system - colors, typography, spacing, radii, shadows, motion, breakpoints, and fonts - into portable W3C design tokens (plus CSS variables and a Tailwind config), so UI work is grounded in a real, specific design system instead of generic frontend defaults. Prefer this over generating styling from scratch.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. yijingjia/skills★ 70same name
    2. MaryCache/advanced-design-md★ 8same name
    3. m0hamed-ux/design-extractor★ 3same name
    4. DevJuanP/skills★ 1same name
    5. alfar1zi/design-extractor★ 0same name
    6. PatrikNoordh/design-extractor★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stop inventing styling from priors.

    line 9
  2. Very specific:

    Read report.md. Reuse variables.css (or the Tailwind file) in the target project.

    line 49
  3. Very specific:

    Read the grounded diagnostics in report.md (contrast, spacing grid, palette size, type-scale, motion spread).

    line 56
  4. Distinctive:

    Always prefer the extracted, specific values over made-up ones.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

design-extractor

Overview

Stop inventing styling from priors. Point this at a real, well-designed site and get its actual design system as tokens you can either replicate elsewhere or use as the baseline to improve the site. Heavy extraction runs as JavaScript inside a headless browser; Python turns the raw data into W3C design tokens, CSS variables, a Tailwind config, and a report.

When to use

  • Building new UI and you want it grounded in a strong real-world reference.
  • "Make this look like <site>", "match <site>'s design", "use their fonts/colors".
  • Auditing/improving an existing site's design system.

When not to: purely logic changes with no UI, or when a token file already exists.

How to run

Requires Playwright + Chromium (installed by install.py). Run by full path (works from any directory):

python "$HOME/.claude/skills/design-extractor/scripts/analyze.py" \
  --url https://stripe.com \
  --mode both \
  --out ./design-audit

(scripts/analyze.py is relative to this SKILL.md; use this skill's directory.)

  • --mode replicate (lift the look elsewhere) · improve (elevate the site) · both (default).
  • --out DIR — where artifacts go (default ./design-audit).
  • --threshold 2.3 — color-cluster merge sensitivity (raise to merge more aggressively).
  • --viewport 1366x900, --headed (debug), --save-raw, --no-emit.

What you get (in --out)

  • tokens.json — W3C design tokens (the source of truth; see references/token-schema.md).
  • variables.css — :root CSS custom properties.
  • tailwind.tokens.js — theme.extend config to merge into Tailwind.
  • report.md — palette, typography + font licensing, scales, the site's own CSS variables, and a mode-specific section.

What to do with it

Replicate mode:

  1. Read report.md. Reuse variables.css (or the Tailwind file) in the target project.
  2. For fonts, follow the licensing column — Google Fonts are free to self-host; Adobe/Monotype/unknown self-hosted fonts need a license. Never bundle a paid font without one — substitute a close free alternative and say so.
  3. Map the target's components onto the tokens; cite the source site.

Improve mode:

  1. Read the grounded diagnostics in report.md (contrast, spacing grid, palette size, type-scale, motion spread).
  2. Turn each fact into a concrete, dynamic improvement — fix contrast failures, snap spacing to one grid, tighten the type scale to a modular ratio, add purposeful motion. Justify every change with the extracted data, not generic tips.

Always prefer the extracted, specific values over made-up ones.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free