design-md
Skill4 starsChanged 6 months agoMITView on GitHub
Load a ready-made brand design system (DESIGN.md) from the awesome-design-md collection into your project. 73 brands available including Linear, Stripe, Vercel, Notion, Figma, Spotify, Tesla, Supabase, and more. Use when the user wants to build a UI that looks like a known brand, wants to use a specific company's design language as a reference, or says things like 'make it look like Linear', 'use Stripe's design system', 'build something Notion-style', 'I want the Vercel aesthetic', or names any specific brand as a visual reference.
65 other projects use a version of this.
Adopted by
Most recently taken up by
- rakaarwaky/agents-arwakytheir own version, first seen Nov 8, 2026
- informaticolorenzo/skill-maestra-publictheir own version, first seen Nov 8, 2026
- ashleysbrain/skillstheir own version, first seen Nov 8, 2026
- pietz/skillstheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- figueroaignacio/ignaciofigueroa.devtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use touchdesigner-mcp, teams-meeting-pipeline and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 7 projects that use this
john-data-chenSkillteams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
Also in 9 projects that use this
aivrarSkillcompetitor-news-monitor
Watch named companies for material news; cited digests.
Also in 6 projects that use this
mae616Skillp5js
p5.js(クリエイティブコーディング)のProcessing由来「コードでスケッチ」思想を軸に、setup/drawループ・座標系・インタラクション・パフォーマンス最適化を整理する。p5.js、Processing、クリエイティブコーディング、ジェネラティブアート、インタラクティブ表現、ビジュアルプログラミング、Canvas描画、パーティクル、フラクタル、ノイズ表現に関する相談で必ず使うこと。ユーザーが「コードでアート」「動くビジュアル」「インタラクティブな描画」と言った場合にも適用する。
Also in 12 projects that use this
jh941213Skilldocs-ci
문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.
Also in 3 projects that use this
jh941213Skilldocs-interfaces
API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.
Also in 3 projects that use this
- +4 more from jh941213
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 65
- loongclaw-ai/loongclaw★ 640same name
- aivrar/portable-hermes-agent★ 239same name
- bifrost-proxy/bifrost★ 168same name
- diodeme/Gold-Band★ 164same name
- jh941213/ADLC-harness★ 125same name
- jh941213/my-cc-harness★ 125same name
- jh941213/my-claude-code-asset★ 125same name
- CaesiumY/ko-design-md★ 75same name
- vobase/vobase★ 60same name
- tdimino/claude-code-minoan★ 41same name
55 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository79 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- 21st-magicSkill
- alpacaSkill
- ask-mattSkill
- autoresearchSkill
- auto-stage-commitSkill
- browser-harnessSkill
- codebase-designSkill
- codeburnSkill
- codex-reviewSkill
- compact-memorySkill
- connect-recommendSkill
- connect-required-verification-informationSkill
- decision-mappingSkill
- delegate-taskSkill
- design-an-interfaceSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- edit-articleSkill
- extract-designSkill
- ffmpegSkill
- find-skillsSkill
- firecrawlSkill
- generateSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-me-codexSkill
- grill-meSkill
- grill-with-docs-codexSkill
- grill-with-docsSkill
- gwSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- kie-aiSkill
- lightragSkill
- llmfitSkill
- loop-meSkill
- migrate-to-shoehornSkill
- notebooklmSkill
- obsidian-vaultSkill
- openspaceSkill
- playwrightSkill
- prototypeSkill
- qaSkill
- request-refactor-planSkill
- resolving-merge-conflictsSkill
- reviewSkill
- roastSkill
- scaffold-exercisesSkill
- session-handoffSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- site-teardownSkill
- skill-discoverySkill
- skilluiSkill
- spline-3dSkill
- stripe-appsSkill
- stripe-best-practicesSkill
- stripe-directorySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Use alongside /skillui (for custom sites) and impeccable (for critique/polish)
- Very specific: line 92
After building, run /impeccable audit to catch anti-patterns, then use the frontend-design skill's comparison workflow to verify fidelity.
- Very specific: line 107
No API keys required — npx getdesign@latest is a public CLI
“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design MD — Brand Design System Loader
Fetches a ready-made DESIGN.md for any of 73 known brands from the awesome-design-md collection. Each file documents a brand's complete design system in plain markdown — colors, typography, components, spacing, and AI agent prompts — so Claude can generate pixel-perfect brand-aligned UI without any Figma exports or scraping.
When to Use
- User names a specific brand as a visual reference ("looks like Linear", "Stripe aesthetic")
- User wants to clone or match the design language of a known product
- User needs a polished starting point without designing from scratch
- Use alongside
/skillui(for custom sites) andimpeccable(for critique/polish)
Available Brands (73 total)
AI & LLM Platforms Claude, Cohere, ElevenLabs, Minimax, Mistral.ai, Ollama, OpenCode.ai, Replicate, RunwayML, Together.ai, VoltAgent, X.ai
Developer Tools Cal, Composio, Cursor, Expo, Framer, Lovable, Raycast, Warp
Backend, Database & DevOps ClickHouse, HashiCorp, IBM, MongoDB, PostHog, Sanity, Sentry, Supabase
Productivity & SaaS Airtable, Intercom, Linear.app, Miro, Notion, Semrush, Superhuman
Design & Creative Tools Clay, Figma, Mintlify, Vercel, Webflow, Zapier
Fintech & Crypto Coinbase, Kraken, Resend, Revolut, Stripe, Wise
E-commerce & Retail Airbnb, Apple, Pinterest, Spotify, Uber
Media & Consumer Tech Nvidia, SpaceX, Tesla, X.ai (see AI above)
Automotive BMW, Ferrari, Lamborghini, Renault, Tesla
Full list: github.com/VoltAgent/awesome-design-md/tree/main/design-md
Workflow
Step 1 — Fetch the DESIGN.md
npx getdesign@latest add <brand-slug>The brand slug is the folder name from the repo (lowercase, e.g. linear.app, stripe, notion).
Examples:
npx getdesign@latest add linear.app
npx getdesign@latest add stripe
npx getdesign@latest add notion
npx getdesign@latest add vercel
npx getdesign@latest add supabase
npx getdesign@latest add figma
npx getdesign@latest add spotify
npx getdesign@latest add teslaThe command drops a DESIGN.md file into your current directory.
Step 2 — Read it into the session
Once generated, read the DESIGN.md using the Read tool so it's in context:
Read the DESIGN.md in the project rootStep 3 — Build with the design system
With DESIGN.md in context, reference it when building UI:
- "Build a pricing page using the design system in DESIGN.md"
- "Create a dashboard hero section following DESIGN.md"
- "Apply the color palette from DESIGN.md to this component"
The file contains pre-written agent prompts for common pages — use those directly.
Step 4 — Polish and audit
After building, run /impeccable audit to catch anti-patterns, then use the frontend-design skill's comparison workflow to verify fidelity.
Decision Guide: Which Tool to Use?
| Situation | Tool |
| Brand is one of the 73 in the collection | /design-md (this skill) |
| Brand/site not in the collection | /skillui — scrape it live |
| No specific brand reference, designing fresh | ui-ux-pro-max --design-system |
| Need to reverse-engineer how a site was built | /site-teardown |
| Audit/polish existing frontend output | /impeccable |
Notes
- Each
DESIGN.mdincludes: visual mood, full color palette with roles, typography hierarchy, component styles (buttons, cards, inputs), spacing scale, shadow/elevation system, do's and don'ts, responsive breakpoints, and AI agent prompts - No API keys required —
npx getdesign@latestis a public CLI - The collection is actively maintained: github.com/VoltAgent/awesome-design-md
- Contributions welcome — see
CONTRIBUTING.mdin the repo
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

