agentsclimarketplace

Design extractor

Skill Dweeb1578/claude-grounding-skills/skills/design-extractor

Anti-slop Claude Code skills: ground Claude in measured reality — live GitHub SOTA ranking + real design-token extraction — instead of training-data priors.

Install
npx -y skills add Dweeb1578/claude-grounding-skills --skill design-extractor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.3 KB, 677 tokens by cl100k_base, as published. Nobody here has run it

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.

Gives 0 of the 12 instructions most css styling skills give in 677 tokens

Counted across 586 of the 596 authors here whose files we hold, read 2026-08-06

  • avoid excessive centered layoutsin 55 of 586, across 12 files
  • bundle code into single HTML filein 54 of 586, across 14 files
  • Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
  • avoid purple gradientsin 51 of 586, across 11 files
  • avoid uniform rounded cornersin 51 of 586, across 11 files
  • avoid Inter fontin 51 of 586, across 11 files
  • edit generated files to develop artifactin 50 of 586, across 10 files
  • animate only transform and opacity propertiesin 43 of 586
  • Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
  • Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
  • use tailwind cssin 39 of 586, across 24 files
  • Use SVG icons instead of emojisin 38 of 586, across 11 files

Said here and by no other author read

  • prefer extracted values over made-up ones
  • read report.md before applying tokens
  • reuse variables.css in the target project
  • map target components onto extracted tokens
  • cite the source site
  • follow font licensing rules

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.