Extract a real design system from any production URL — colors, typography, spacing, breakpoints, motion, interaction states — and stream it as a portable DESIGN.md your coding agent can actually read.
Web · Benchmarks · CLI on npm · Examples
npx @designmdcc/cli stripe.com > DESIGN.mdThat's the whole flow. No account, no config, no API key. The command streams a measured DESIGN.md spec for stripe.com to stdout; redirect it into a file and hand it to your AI coding agent.
For repeat use, install globally:
npm install -g @designmdcc/cli
dmd stripe.com > DESIGN.mdRequires Node 18+.
URL → Live browser measurement → Structured tokens → DESIGN.md → Your AI agent
DesignMD opens the URL in a headless browser, measures the real visual system — colors from computed styles, typography from the cascade, breakpoints from live @media rules, hover/focus states from the CSSOM — and synthesizes a portable specification.
The output is the kind of file a senior engineer would actually use to rebuild the brand. Drop it into Cursor, Claude Code, Windsurf, Aider, Copilot, or paste it into any LLM chat. The model gets ground truth instead of guesses.
dmd <url> # stream DESIGN.md to stdout
dmd <url> --out=PATH # write to a file
dmd <url> --json # extract tokens only (no LLM call — instant, no quota)
dmd <url> --force # bypass cache, re-extract from live page
dmd <url> --quiet # suppress progress messages on stderr
dmd --help
dmd --version# Pipe into a project file
dmd stripe.com > ./design/stripe.md
# Send to clipboard
dmd https://linear.app | pbcopy
# Token-only extraction (machine-readable, free, instant)
dmd vercel.com --json | jq '.colors'
# Self-hosting / regional endpoint
DESIGNMD_API=https://my-designmd.internal dmd notion.sostdout always carries the markdown (or JSON). Progress lines go to stderr, so pipes stay clean.
The generated DESIGN.md is purpose-built for LLM context windows. Drop it in once; reference it from your agent's rules file.
Add to your project's CLAUDE.md:
When building any UI in this project, read @DESIGN.md before generating code.
Use the colors, typography, and spacing from that file exactly — do not invent
brand values.Add to .cursor/rules (or .cursorrules):
Read DESIGN.md before writing UI code. Use its color palette, type scale,
and spacing values exactly. Every brand value should trace back to the file.
Same pattern — every modern coding agent supports a project-root rules file. Reference DESIGN.md from it.
Full integration guide: docs/ai-workflows.md.
A snippet from examples/DESIGN-stripe.md:
## Color Palette & Roles
### Primary
- **Brand Indigo (#0a2540)** — Hero typography, primary footer surface
- **Stripe Purple (#635bff)** — Primary buttons, focus rings, link accents
### Surface
- **Pure White (#ffffff)** — Page background, card surface
- **Cool Mist (#f6f9fc)** — Secondary surface, alternating sections
### Typography
| Role | Font | Size | Weight | Line Height |
|---------|-----------|------|--------|-------------|
| Display | Sohne Var | 64px | 600 | 1.05 |
| H1 | Sohne Var | 40px | 600 | 1.15 |
| Body | Sohne Var | 18px | 400 | 1.6 |
| Code | Sohne Mono| 14px | 400 | 1.5 |
### Breakpoints (measured live)
- 480px · 600px · 768px · 880px · 1024px · 1200px · 1440pxFull file: DESIGN-stripe.md · Live page
Eight production sites, each measured live. Click a card for the full DESIGN.md.
![]() Stripe |
![]() Linear |
![]() Vercel |
![]() Notion |
![]() Anthropic |
![]() Mercury |
![]() Figma |
![]() Airbnb |
A larger reference catalog — 56 measured sites across 13 categories — is live at designmd.cc/benchmarks.
| Approach | Failure mode |
|---|---|
| Agent guesses from prompt | Hallucinates plausible-looking but wrong colors, fonts, spacing |
| Designer hand-documents tokens | Stale within weeks; doesn't scale |
| Screenshot → vision model | Loses structural information; treats decorative pixels as design intent |
| Static design-system catalog | Hand-curated, biased to designer aesthetics, doesn't match a real brand |
DesignMD measures live, then formalizes the measurement as a markdown spec that survives the round-trip into an LLM context window. The file is portable, diff-able, and re-generable when the source site evolves.
The CLI uses distinct exit codes so scripts and agents can react correctly:
| Code | Meaning |
|---|---|
0 |
Success |
1 |
User error (bad URL, unsupported flag, refused extraction) |
2 |
Transient — try again (rate limit, server busy, timeout) |
3 |
Network error |
Anonymous use: 5 generations per day per IP-bucket. The --json flag does not count against this — it skips the LLM step entirely and returns the raw token extraction.
Per-user API keys with higher quotas will arrive alongside account auth.
This repository is the public developer surface. It contains:
- Sample
DESIGN.mdoutputs from the live catalog (examples/) - FAQ and AI-coding-agent integration guide (
docs/) - UI screenshots (
screenshots/) - The CLI's published documentation (this README)
It does not contain:
- The extraction pipeline or browser instrumentation
- LLM prompts and synthesis logic
- Server source, rate-limiting, caching, or auth internals
- Schema definitions or operator tooling
For commercial licensing or production-access inquiries, reach out — adityaraj.info.
| Variable | Default | Purpose |
|---|---|---|
DESIGNMD_API |
https://designmd.cc |
Override the API base URL (self-hosting) |
This is a curated developer surface, not a fully open-source project. We welcome:
- Bug reports on designmd.cc — open an issue here
- Benchmark suggestions — open an issue with a URL you want measured
- Documentation improvements in
docs/ - Better sample examples — PRs against
examples/welcome
For larger changes, open an issue first to discuss. See CONTRIBUTING.md.
MIT — covers the materials in this repository: the CLI source, sample DESIGN.md outputs, documentation, screenshots, and example thumbnails.
The MIT license does not extend to:
- The DesignMD production source code, automation, or infrastructure
- The token-extraction pipeline and prompts
- The DesignMD name, logo, and brand identity
Built by Aditya Raj. Thanks to the designers and engineers behind the modern web whose publicly accessible visual systems make benchmarking and design research possible.







