I'll generate a DESIGN.md from promptbase.com. Let me first read the skill's reference files, then extract the site's real design tokens. Read 2 files I'll use the in-app Browser (real computed styles — method A). Let me navigate to promptbase.com and extract. Loading AI Prompts | PromptBase: The #1 Marketplace for AI Prompts promptbase.com · Opened in Browser Used 3 tools Let me capture a screenshot and read key components for the visual context. Used 2 tools Screenshot is timing out. I'll gather component details via JavaScript instead, which is more precise anyway. Used Claude Browser: javascript tool Now I understand the system — a dark navy theme with a mint-green accent. Let me capture the accent/CTA elements and surface layers precisely. Used Claude Browser: javascript tool One more targeted check — the search submit button (the other half-pill) to pin the primary action color. Used Claude Browser: javascript tool I have solid evidence. Writing the DESIGN.md now. Created DESIGN.md +252 -0 Done. Extracted via method A (real computed styles from the in-app browser — no source guessing). 📄 Saved to: DESIGN.md What promptbase.com's design system turned out to be A near-monochromatic dark-navy marketplace. The whole visual hierarchy runs on three stacked navy surfaces plus off-white text — almost no colorful UI at all: Canvas #1a1a2e → chrome #232339 → controls #3a3a5c, all text in #f8f9fa One accent, strictly rationed: a Stripe-style mint success chip (#cbf4c9 field / #0e6245 text) used only for tiny 8px discount tags. Even the search button is the same navy as its field — nothing is a bright CTA. Type: a single family, Finlandica, weights 400/500/600; tight 1.2 line-height on headings (48px display, 18px subheads), comfortable 1.5 on 14px body. Geometry: 16px card corners (the dominant radius), 48px full-pill search, 50% avatars, 2px chips; depth from soft shadows (rgba(0,0,0,0.15) 2px 3px 9px) rather than borders. Base unit: 8px. The DESIGN.md includes named tokens with roles, the full type scale, spacing/radius/elevation, six component specs (nav, hero, split-pill search, tile, chip, headline), site-specific Do's & Don'ts, copy-paste CSS custom properties + Tailwind v4 @theme blocks, and an agent prompt cheat-sheet. Two notes on honesty: The site declared no :root custom properties — every value here is a real computed style, clustered by frequency. I omitted the "Similar Brands" section (no confident look-alike) and did not fabricate a "Similar/Elevation guess" — elevation is backed by measured shadows. Want me to also drop just the CSS-variables block, or save the file somewhere inside the repo instead of the scratchpad?