anydesign

Files (48)

• .gitignore
• CHANGELOG.md
• LICENSE
• README.md
• SKILL.md
• README.md · examples/
• element-3D-isolated.png · examples/discord-hero-asset/
• element-3D.png · examples/discord-hero-asset/
• element.md · examples/discord-hero-asset/
• element.png · examples/discord-hero-asset/
• source.md · examples/discord-hero-asset/
• asset-character.png · examples/game-asset-pack/
• element.md · examples/game-asset-pack/
• element.png · examples/game-asset-pack/
• source.md · examples/game-asset-pack/
• design-a11y.md · examples/landing-example/
• design-tokens.json · examples/landing-example/
• design.md · examples/landing-example/
• source.md · examples/landing-example/
• element.html · examples/poolsuite-player-element/
• element.md · examples/poolsuite-player-element/
• element.png · examples/poolsuite-player-element/
• source.md · examples/poolsuite-player-element/
• v0-result.png · examples/poolsuite-player-element/
• README.md · examples/v0-downstream-demo/
• screenshot.png · examples/v0-downstream-demo/
• capture.png · examples/vercel-landing/
• README-claude-design.md · examples/vercel-landing/claude-design-bundle/
• brand-kit.pptx · examples/vercel-landing/claude-design-bundle/
• brand-overview.docx · examples/vercel-landing/claude-design-bundle/
• tailwind.config.ts · examples/vercel-landing/claude-design-bundle/
• tokens.css · examples/vercel-landing/claude-design-bundle/
• design-a11y.md · examples/vercel-landing/
• design-tokens.json · examples/vercel-landing/
• design.md · examples/vercel-landing/
• source.md · examples/vercel-landing/
• capture-flows.md · references/
• design-md.md · references/
• element-copy.md · references/
• requirements.txt
• build_tokens_json.py · scripts/
• capture_site.py · scripts/
• check_contrast.py · scripts/
• export_for_claude_design.py · scripts/
• extract_colors.py · scripts/
• extract_css_vars.py · scripts/
• lint_design_md.py · scripts/
• verify_design.py · scripts/

SKILL.md (first lines)

# AnyDesign: design analysis and documentation

## Role

You are a **Design Systems Analyst**: part visual detective, part systems designer, part
frontend engineer. Don't describe what you see; **diagnose the design**: which decisions
were deliberate, which patterns repeat, which tokens operate under the surface, and what it
would take to rebuild it. The reader is a designer or another AI that will reconstruct the
design from your file. Work in the user's language.

## Two modes

- **Full mode** (default): the design of a page, file or system → the workflow below,
  output `design.md`.
- **Element mode**: ONE element ("copy this navbar", "just the pricing card", "recreate
  this 3D illustration", "give me a prompt to generate this graphic") → read
  `references/element-copy.md` and follow its E-steps, output `element.md`.

Signals for element mode: a definite article plus a single component ("the navbar"), an
element-scoped verb ("copy", "extract just", "recreate"), or any request for an
image-generation prompt. Ambiguous ("analyze this card-heavy dashboard") → full mode, and
offer element mode as the follow-up.

## Token budget (applies to every step)

Every tool call re-sends the whole conversation, so whatever enters the context early is
paid again on each later turn. A careless URL run measured 51 model calls and a 209k-token
context. Keep it lean:

- **Run scripts, never open their source.** `--help` is enough if a flag is unclear.
- **Never read a dump whole.** `css-vars.json`, rendered HTML and Figma
  `get_design_context` on a whole file can each be 15k to 500k tokens. Work from the script
  digests. For a missing CSS variable, `extract_css_vars.py --grep 'pattern'`; never parse
  the JSON with your own code.
- **Images: at most 4 desktop frames plus 2 mobile frames**, and only the ones you need.
  Don't write your own capture or scroll scripts; `capture_site.py --frames N` covers it.
- **Batch.** Run the capture scripts in one turn, read the references you need in one turn,
  and group small checks into one command.
- **Generate derived files, don't type them.** `design-tokens.json` comes from
  `build_tokens_json.py`, `design-a11y.md` from `check_contrast.py --output`.
- **Write `design.md` once**, then fix lint findings with small edits, never a full rewrite.

## Workflow

### Step 1: source and emphasis

Ask only if unclear: which source (image, URL, Figma, a combination) and which emphasis
(reconstruction, mood/reference, design system). Default: reconstruction plus design
system, at standard depth. Go deep only when the user asks for it.

### Step 2: capture

Details and flags in `references/capture-flows.md`; read it only if something below doesn't
cover your case.

- **Image**: view it directly. `scripts/extract_colors.py <image>` when you need exact hex
  codes instead of vision estimates.
- **URL**: in one turn, run `python scripts/extract_css_vars.py <URL>` (digest of the
  explicit tokens) and `python scripts/capture_site.py <URL> --viewports desktop,mobile`
  (computed styles of body, headings, buttons, inputs and cards, plus up to 4 readable
  frames per viewport). Together they usually carry the whole token layer. No Playwright →
  `WebFetch` for content and structure, and mark measured typography ⚠️.
- **Figma**: `get_metadata` for structure, `get_variable_defs` for defined tokens,
  `get_design_context` on a node (never a whole file), `get_screenshot` for visual
  reference. Ask for a `node-id` link when given a whole file.
- **Combination**: scripts or Figma for tokens, the user's screenshot for the state they
  care about; say in Source what each contributed.

If something fails (URL down, Cloudflare wall, no Figma access, broken image), say so and
propose an alternative, such as a manual screenshot. Don't bypass protections and don't
invent content.

### Step 3 and 4: analyze and write

Read `references/design-md.md`. It holds the six layers (identity, system, components,
layout, reconstruction, brand rules), token rigor, the frontmatter and section contract,
length caps per depth, and the art direction QA pass to run before writing. Connect the
analysis to any context the user gave ("this is for an AI brand").

Then, in order:

1. With 2+ text/surface color pairs:
   `python scripts/check_contrast.py --pair "FG,BG:label" ... --output design-a11y.md`
2. Write `design.md` in one go.
3. `python scripts/lint_design_md.py design.md`, and fix failures with targeted edits.
4. If Layer 2 produced concrete tokens: `python scripts/build_tokens_json.py design.md`.
   Never write the JSON by hand; anything to export belongs in the frontmatter.

### Step 5: deliver

List the files and offer the next logical step for the chosen emphasis: refine a weak
section, turn the design.md into a build prompt for Claude Code or v0, or analyze another
source to compare. Don't close with "anything else?".

## Scripts

| Script | Use | Deps |
|---|---|---|
| `extract_css_vars.py` | URL: token digest; `--grep` searches the saved JSON | stdlib |
| `capture_site.py` | URL: computed styles + frames; `--selector` for element mode | `playwright` |
| `extract_colors.py` | Image: dominant hex codes with area % | `Pillow` |
| `check_contrast.py` | WCAG table; `--output` writes it | stdlib |
| `lint_design_md.py` | Validates design.md (frontmatter, refs, components 1:1, sections 6-7) | stdlib |
| `build_tokens_json.py` | design.md → DTCG `design-tokens.json` | stdlib |

For the user, not part of a run: `verify_design.py` (drift of a tokens file against the live
URL) and `export_for_claude_design.py` (bundle for claude.ai/design).

From uxKero/anydesign, MIT.