BranchesTags

Repository files navigation

designmd.supply

A supply of design md, generated. Drop in any public domain — get back a Google-spec DESIGN.md ready to feed an AI agent.

designmd.supply is a small Next.js app that turns any website into a self-contained design system document. It pulls brand identity, design tokens, a hero screenshot, and the live page Markdown, then composes them into a DESIGN.md file with YAML frontmatter and the canonical sections (Overview, Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).

Powered by Context.dev

The whole pipeline runs on four endpoints from the Context.dev API:

Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.

The four payloads converge in lib/design-md.ts, where they're shaped into a single prompt and sent through the Vercel AI Gateway to produce the final DESIGN.md.

Get a free Context.dev key at context.dev.

Quickstart

npm install
cp .env.example .env
npm run dev

Then open http://localhost:3000 and search for any domain.

Environment variables

CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=

The designmd_* prefix matches the variables provisioned by the Turso integration on the Vercel Marketplace, so on Vercel they're injected automatically. Locally, copy them from the project's Vercel dashboard into .env. If they're absent, the app still works — it just falls through to the live Context.dev APIs on every request with no cache.

How it works

 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide JSON as the primary token source and the screenshot + page Markdown as supporting evidence for tone, components, and layout — so values come from real data rather than the model's imagination.

Project layout

app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso

The four Context.dev payloads (styleguide, brand, screenshot, markdown) and the final composed DESIGN.md are all cached in a single Turso table, domain_cache, keyed by (domain, kind). The schema is created lazily on first use — there's no migration step.

  • First request for a domain hits Context.dev + the LLM and writes every payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains with a cached designmd row from Turso, so the build only pre-renders pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to pull brand + screenshot for every curated domain in one round trip.

Cache writes are best-effort — if Turso is unreachable, the request still succeeds, the user just doesn't get a cached copy. The same applies if the env vars are missing entirely (see above).

To add a domain to the curated directory, append it to TOP_DOMAINS in lib/domains.ts. The first visit will populate the cache.

Scripts

npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit

Tech stack

Contributing

Issues and PRs welcome. To add a domain to the curated directory, append it to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.

License

MIT

About

A supply of the world's designmds

designmd.supply

Resources

Readme
MIT license
Activity
Custom properties

Stars

264 stars

Watchers

1 watching

Forks

29 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
BranchesTags
Repository files navigation
designmd.supply
A supply of design md, generated. Drop in any public domain — get back a
Google-spec DESIGN.md ready to feed an AI agent.
designmd.supply is a small Next.js app that turns any website into a
self-contained design system document. It pulls brand identity, design tokens,
a hero screenshot, and the live page Markdown, then composes them into a
DESIGN.md file with YAML frontmatter and the canonical sections (Overview,
Colors, Typography, Layout, Elevation, Shapes, Components, Do's and Don'ts).
Powered by Context.dev
The whole pipeline runs on four endpoints from the
Context.dev API:
Context.dev APIWhat we use it for
Styleguide API — web.extractStyleguidePrimary source of truth for design tokens: colors, typography, spacing, radii, components.
Brand API — brand.retrieveLogos, backdrops, brand colors, slogan, industry classification — used to render the directory and the canvas hero.
Screenshot API — web.screenshotHigh-quality homepage capture, fed to the model as visual context for tone and layout.
Markdown API — web.webScrapeMdClean Markdown of the live page so the model can ground component and copy guidance in real content.
The four payloads converge in
lib/design-md.ts, where they're shaped into a single
prompt and sent through the Vercel AI Gateway
to produce the final DESIGN.md.
Get a free Context.dev key at
context.dev.
Quickstart
npm install
cp .env.example .env
npm run dev
Then open http://localhost:3000 and search for any domain.
Environment variables
CONTEXT_DEV_API_KEY= # https://context.dev
VERCEL_AI_GATEWAY_API_KEY= # https://vercel.com/ai-gateway# Turso (Vercel Marketplace integration — auto-injected on Vercel)
designmd_TURSO_DATABASE_URL=
designmd_TURSO_AUTH_TOKEN=
The designmd_* prefix matches the variables provisioned by the
Turso integration on the Vercel Marketplace,
so on Vercel they're injected automatically. Locally, copy them from the
project's Vercel dashboard into .env. If they're absent, the app still
works — it just falls through to the live Context.dev APIs on every request
with no cache.
How it works
 ┌──────────────────────────────────────────┐
│ Domain in (any URL) │
└──────────────────────────────────────────┘
│
▼
Turso cache hit? ──► serve cached payload
│
▼ (miss)
┌──────────────┬───────────┴──────────┬──────────────┐
▼ ▼ ▼ ▼
Styleguide API Brand API Screenshot API Markdown API
(tokens) (logos, colors) (hero image) (page text)
│ │ │ │
└──────────────┴──────────┬───────────┴──────────────┘
▼
Prompt assembly (lib/design-md.ts)
▼
LLM via Vercel AI Gateway
▼
DESIGN.md (YAML + Markdown)
▼
write back to Turso

The four Context.dev calls run in parallel. The model receives the styleguide
JSON as the primary token source and the screenshot + page Markdown as
supporting evidence for tone, components, and layout — so values come from
real data rather than the model's imagination.
Project layout
app/
api/
brand/ GET — Context.dev Brand API proxy (Turso-cached)
styleguide/ GET — Context.dev Styleguide API proxy (Turso-cached)
screenshot/ GET — Context.dev Screenshot API proxy (Turso-cached)
design-md/ GET — Turso cache lookup
POST — compose DESIGN.md from the three payloads + Markdown
guides/[domain]/ route for an individual generated guide
page.tsx home with search + directory of curated domains
components/ UI: directory, search, canvas, orchestration, copy block
lib/
design-md.ts prompt + spec summary
domains.ts curated list of domains shown on the home page
turso.ts libSQL client + cache helpers (get/set/batch/listDomains)

Caching with Turso
The four Context.dev payloads (styleguide, brand, screenshot, markdown) and
the final composed DESIGN.md are all cached in a single Turso table,
domain_cache, keyed by (domain, kind). The schema is created lazily on
first use — there's no migration step.
  • First request for a domain hits Context.dev + the LLM and writes every
payload back to Turso.
  • Subsequent requests for the same domain serve straight from Turso.
  • generateStaticParams for /guides/[domain] reads the set of domains
with a cached designmd row from Turso, so the build only pre-renders
pages that actually have content.
  • Homepage directory uses a single batched read (getCachedBatch) to
pull brand + screenshot for every curated domain in one round trip.
Cache writes are best-effort — if Turso is unreachable, the request still
succeeds, the user just doesn't get a cached copy. The same applies if the
env vars are missing entirely (see above).
To add a domain to the curated directory, append it to TOP_DOMAINS in
lib/domains.ts. The first visit will populate the cache.
Scripts
npm run dev # Next dev server
npm run build # production build
npm run start # serve the production build
npm run lint # eslint
npm run typecheck # tsc --noEmit
Tech stack
Contributing
Issues and PRs welcome. To add a domain to the curated directory, append it
to TOP_DOMAINS in lib/domains.ts — the cache populates on first visit.
License
MIT
About
A supply of the world's designmds
designmd.supply
Resources
Readme
MIT license
Activity
Custom properties
Stars
264 stars
Watchers
1 watching
Forks
29 forks
Report repository
Releases
Packages
Used by
Contributors
Languages