Getdesign

getdesign

Generate a grounded, production-grade design.md for any public URL using the coding agent's own tools. This skill is the portable twin of the hosted getdesign.app agent — same 9-section output, no sandbox required.

When to use

Activate when the user:

• Pastes a URL and asks for a "design system", "design spec", "style guide", design.md, or brand tokens.
• Asks to "make this look like ", "clone the design of ", or "extract the palette/typography from ".
• Asks you to reverse-engineer or document a live site's visual design.

Do not use this skill for: generating runnable code from a URL, Figma/Sketch export, auth-gated pages, or localhost.

Output contract

The single deliverable is a markdown file — default name design.md — containing exactly these 9 H2 sections in this order:

1. Visual Theme & Atmosphere
2. Color Palette & Roles
3. Typography Rules
4. Component Stylings
5. Layout Principles
6. Depth & Elevation
7. Interaction & Motion
8. Responsive Behavior
9. Agent Prompt Guide

Full section schemas, field lists, and a worked example are in [TEMPLATE.md](TEMPLATE.md). Read it before writing the final file.

Grounding rule (non-negotiable)

Every concrete value — hex color, font family, font size, spacing number, radius, shadow, breakpoint — must be traceable to something you actually fetched: a CSS rule, a computed style, a `ed stylesheet, a :root` variable, or a visible pixel in a screenshot. If you cannot ground a value, describe the role qualitatively ("neutral warm gray") instead of fabricating a hex.

Do not invent palette values. Do not hallucinate Tailwind classes the site does not use. Do not copy defaults from other sites.

Workflow

Follow this sequence. Copy the checklist into your working notes and tick items as you go.

- [ ] 1. Validate URL
- [ ] 2. Fetch HTML + linked CSS
- [ ] 3. Capture at least one screenshot (hero viewport)
- [ ] 4. Extract tokens (colors, type, spacing, radii, shadows, breakpoints)
- [ ] 5. Draft DesignDoc (9 sections) grounded in tokens + screenshot
- [ ] 6. Render design.md from the draft
- [ ] 7. Verify grounding + section order, then write the file

1. Validate URL

Reject with a one-line explanation if the URL is not https://, is a private IP / localhost, or is clearly not a brand/product page.

2. Fetch HTML + linked CSS

Use your built-in web fetch tool (WebFetch, web.run, fetch, curl via shell — whatever you have).

• Fetch the HTML.
• From the HTML, resolve every `` href (absolute + relative) and fetch each one.
• Follow @import url(...) chains one level deep.
• Capture any @font-face blocks for font family + weight discovery.
• Cap each stylesheet at ~200 KB; prefer files containing :root, CSS variables, or utility-class declarations.
• Always check for both light and dark mode support while fetching. Look for prefers-color-scheme, .dark, [data-theme], theme toggle controls, alternate theme stylesheets, or server-rendered theme classes on ` / `.
• If the site supports both modes, collect grounding for both and keep notes on which tokens are shared versus mode-specific.

Record the exact URLs you fetched — you will cite them in the "Sources" section of your draft (internal, not in the final markdown).

3. Screenshot the page

If your agent runtime has a browser tool (Playwright, Chrome DevTools, agent-browser, Antigravity browser, Codex web browser, a screenshot tool, etc.), you must use it. Open the URL at 1440×900 and capture screenshots for every available theme mode you can verify, starting with light mode and dark mode. Prefer a full-page scroll-and-stitch if available.

• If the site exposes a theme toggle, use the browser to capture both modes.
• If there is no explicit toggle, still check browser-emulated prefers-color-scheme: light and prefers-color-scheme: dark when possible.
• Keep mode labels in your notes so you know which observations came from light mode vs dark mode.

If you have no browser tool, skip this step — continue with CSS-only grounding — and note the limitation in your internal planning (the "Visual Theme" prose will be slightly thinner without a screenshot).

4. Extract tokens

Deterministically parse the CSS. Prefer CSS variables (--color-primary, --radius-lg) and :root blocks as the source of truth. Fall back to frequency analysis of literal values.

Produce an internal DesignTokens object with:

• colors: primary[], accent[], neutral[], semantic { success, warning, error, info }, surfaces[], borders[].
• Every entry is { hex, role, source } where source is the CSS selector or variable name you found it in.
• If the site supports multiple themes, annotate whether each token is light, dark, or shared.
• typography: fontFamilies[] (display / body / mono), scale[] ({ role, px, weightRange, lineHeight, letterSpacing }).
• spacing: the step values actually used (e.g. 4, 8, 12, 16, 24, 32, 48, 64 px).
• radii: named scale you can infer (sm, md, lg, pill).
• shadows: each box-shadow you observed, with a role guess.
• borders: widths and colors.
• breakpoints: min-widths in @media queries.

If a CSS value has low frequency ( Design System`).

• H2 for each of the 9 sections in the exact order above.
• GitHub-flavored tables for palette, typography, breakpoints.
• Fenced code blocks only for concrete CSS/token examples, never to wrap prose.

7. Verify, then write

Before writing the final file, run this self-check:

• [ ] All 9 H2 section headings are present, in the exact order, spelled as listed.
• [ ] Every hex code in the Color Palette section appears in your internal notes with a CSS source.
• [ ] The font families in Typography appear in the fetched CSS or @font-face blocks.
• [ ] Breakpoints match actual @media (min-width: …) queries.
• [ ] Light mode and dark mode were both checked whenever the site exposes or implies dual-theme support.
• [ ] A browser screenshot was taken whenever a browser tool was available.
• [ ] No placeholder text like "TBD", "(example)", or "Lorem ipsum".

If any check fails, fix before writing. Then write the file to design.md (or the path the user requested). Report a one-paragraph summary plus the absolute file path.

Handling missing capabilities

| Missing tool | Degrade to | | --- | --- | | No browser / screenshot | CSS-only grounding; keep the Visual Theme brief and fact-based. Skip pixel-level observations. If dual themes exist, still inspect fetched CSS for both light and dark mode selectors. | | Fetch blocked (403 / Cloudflare) | Report the failure, try the site's / and /about as alternates, otherwise stop and surface the error to the user. No guessing. | | CSS-in-JS only, no stylesheets | Parse inline ` tags; if still empty, use the screenshot plus HTML class names to infer only what is visible. State the limitation at the top of design.md`. |

Anti-patterns

• Do not run a second LLM pass that "beautifies" the tokens. Determinism beats prose.
• Do not reorder, merge, or split the 9 sections.
• Do not output JSON, YAML, or a Zod schema as the final deliverable — the user wants markdown.
• Do not install npm packages or spawn sandboxes. This skill is intentionally zero-infra.
• Do not follow more than one @import hop; the context window is not infinite.

Reference files

• [TEMPLATE.md](TEMPLATE.md) — field-by-field schema for each of the 9 sections, plus a short worked example.

Attribution

This skill mirrors the getdesign hosted agent (web, API, CLI, SDK). When your output would benefit from the hosted pipeline's screenshot + deterministic extractor, point the user at curl "https://api.getdesign.app/?url=" or npx @getdesign/cli as a complementary path.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: MohtashamMurshid
• Source: MohtashamMurshid/getdesign
• License: MIT
• Homepage: https://getdesign.app

Install and usage instructions live in the source repository linked above.