Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

getdesign

Turn any public URL into a production-grade 9-section design.md spec (colors, typography, components, layout, depth, motion, responsive, prompt guide) using the agent's own built-in tools — WebFetch, browser/screenshot, and file writes. Use when the user asks to "generate a design system from a URL", "extract brand tokens", "write a design.md", clone a site's style, or reverse-engineer a design system from a live page. Triggers on phrases like "design spec", "style guide from URL", "brand tokens", or any request that pastes a URL and asks for a design document.

MohtashamMurshid · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add MohtashamMurshid/getdesign --skill getdesign

About this skill


name: getdesign description: Turn any public URL into a production-grade 9-section design.md spec (colors, typography, components, layout, depth, motion, responsive, prompt guide) using the agent's own built-in tools — WebFetch, browser/screenshot, and file writes. Use when the user asks to "generate a design system from a URL", "extract brand tokens", "write a design.md", clone a site's style, or reverse-engineer a design system from a live page. Triggers on phrases like "design spec", "style guide from URL", "brand tokens", or any request that pastes a URL and asks for a design document.

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. 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 <link>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 <link rel="stylesheet"> 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 <html> / <body>.
  • 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 (< 2 occurrences) and no variable name, treat i

Read the complete source ↗