agentleFS
NiseelNiseel/ai-sdlc-starter/.claude/skills/extract-design/SKILL.md

extract-design

Skill1 starsChanged 58 days agoMITView on GitHub

Extract the full design language from any public website URL with designlang (colors, typography, spacing, radii, shadows, gradients, components, breakpoints, motion, WCAG score). Use when the user says 'extract design', 'get design system', 'design language', 'design tokens', 'what colors/fonts does this site use', or when the design-system skill needs raw data from a reference site.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the designlang extractor against one public URL and read what it found.

    line 14
  2. Very specific:

    Use the pinned, audited release.

    line 20
  3. Distinctive:

    If Google Chrome is installed (fast path, skips the 150 MB Chromium download):

    line 22
  4. Very specific:

    If Chrome is not installed, drop both npm_config_ignore_scripts=true and --system-chrome.

    line 30
  5. Very specific:

    Never pass --smart: it sends a page digest to a third-party LLM API.

    line 35
  6. Very specific:

    Never pass --cookie / --cookie-file unless the user gives them explicitly.

    line 36
  7. Distinctive:

    Read, in this order:

    line 44
  8. Very specific:

    Do not copy the generated Tailwind/shadcn/theme files into the project unless the user asks for them.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 5 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

Extract Design Language

<!-- Vendored from github.com/Manavarya09/design-extract (MIT) - see UPSTREAM.md. Local changes: version pinned, lifecycle scripts skipped, output dir fixed, steps 3-4 point at the design-system skill instead of copying themes. -->

Run the designlang extractor against one public URL and read what it found. This skill produces RAW data only. Turning it into the project's rules is the job of the design-system skill.

1. Run the extraction (pinned version)

Use the pinned, audited release. Do not use @latest.

If Google Chrome is installed (fast path, skips the 150 MB Chromium download):

npm_config_ignore_scripts=true npx -y designlang@12.21.0 <url> \
  --system-chrome --depth 2 --screenshots --wait 2500 --no-history \
  -o .design-extract/<host>

If Chrome is not installed, drop both npm_config_ignore_scripts=true and --system-chrome. The package postinstall then downloads Playwright Chromium.

  • Dark-mode sites with a light variant: add --dark.
  • Single-page apps that render late: raise --wait (ms).
  • Never pass --smart: it sends a page digest to a third-party LLM API.
  • Never pass --cookie / --cookie-file unless the user gives them explicitly.

2. Read the results

ls .design-extract/<host>

Read, in this order:

  1. *-DESIGN.md - compact summary (colors, type, layout, elevation, shapes).
  2. *-variables.css - every CSS custom property the site declares. Most exact source for colors.
  3. *-design-tokens.json - W3C tokens, if a value is missing above.
  4. screenshots/*.png - hero, nav, buttons, cards; view them to understand the style.

3. Known extractor limits (verify before trusting)

  • Fluid type and spacing: sites that scale with vw (common on Webflow) report inflated font sizes and a noisy spacing scale. Measure the live page with a browser tool at 1440 px width before using any size.
  • Background role: on dark sites background may be reported as #ffffff. Trust the "Dominance (share of painted area)" line instead.
  • Breakpoints may print as [object Object]px. Read them from the CSS instead.
  • Colors, font families, shadows and gradients are usually exact.

4. Present findings, then hand off

Tell the user: primary palette (hex), font families, spacing base, radius and shadow habits, WCAG score, component patterns, and what you could not verify.

Then continue with the design-system skill to curate the project rules. Do not copy the generated Tailwind/shadcn/theme files into the project unless the user asks for them.

.design-extract/ is scratch output. It stays out of git.

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.