design-md
Skill1 starsChanged 6 months agoMITView on GitHub
Create and maintain DESIGN.md files that define a visual identity and design system for software projects. Use this skill when the user asks to create a DESIGN.md, set up a design system document, define brand colors/typography/spacing as code, generate design tokens, or establish visual identity guidelines for a project. Also use when the user mentions "design system", "design tokens", "visual identity", "brand guidelines", "DESIGN.md", or wants to document their app's look and feel in a machine-readable format that AI agents can follow.
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 repository4 other files it gives its agents.
- capcut-editorSkill
- flutter-clean-archSkill
- git-conventionSkill
- intellij-pluginSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Create self-contained DESIGN.md files that define a project's visual identity as structured design tokens and human-readable guidance.
- Distinctive: line 252
When asked to create a DESIGN.md:
“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 Skill
Create self-contained DESIGN.md files that define a project's visual identity as structured design tokens and human-readable guidance. Based on the DESIGN.md spec by Google Labs.
What is DESIGN.md
A plain-text design system document that serves as a living source of truth for both humans and AI agents. It contains:
- YAML frontmatter — machine-readable design tokens (colors, typography, spacing, etc.)
- Markdown body — human-readable design rationale and usage guidance
File Structure
---
version: alpha
name: <Design System Name>
colors:
primary: "#..."
secondary: "#..."
typography:
h1:
fontFamily: ...
fontSize: ...
fontWeight: ...
lineHeight: ...
letterSpacing: ...
spacing:
base: ...
sm: ...
md: ...
lg: ...
rounded:
sm: ...
md: ...
full: ...
components:
button-primary:
backgroundColor: "{colors.primary}"
textColor: "#..."
rounded: "{rounded.md}"
---
# Design System Name
## Overview
...
## Colors
...
## Typography
...
## Layout
...
## Elevation & Depth
...
## Shapes
...
## Components
...
## Do's and Don'ts
...Frontmatter Schema
Top-level
version: <string> # optional, current version: "alpha"
name: <string> # required, name of the design system
description: <string> # optional
colors: # map<string, Color>
<token-name>: <Color>
typography: # map<string, Typography>
<token-name>: <Typography>
rounded: # map<string, Dimension>
<scale-level>: <Dimension>
spacing: # map<string, Dimension | number>
<scale-level>: <Dimension | number>
components: # map<string, map<string, string>>
<component-name>:
<token-name>: <string | token reference>Types
Color: Hex string starting with # in SRGB (e.g., "#1A1C1E", "#F7F5F280").
Typography:
fontFamily: <string> # e.g., "Inter", "Public Sans"
fontSize: <Dimension> # e.g., "48px", "2rem"
fontWeight: <number> # e.g., 400, 600, 700
lineHeight: <Dimension | number> # e.g., "24px", 1.6
letterSpacing: <Dimension> # e.g., "-0.02em", "0.1em"
fontFeature: <string> # optional, font-feature-settings
fontVariation: <string> # optional, font-variation-settingsDimension: String with unit suffix. Valid units: px, em, rem.
Token Reference: Wrapped in curly braces pointing to another token. Example: {colors.primary}, {typography.body-md}, {rounded.md}.
Sections
Sections appear in this order. Omit sections that are not relevant to the project.
1. Overview (also "Brand & Style")
Holistic description of the product's look and feel. Defines brand personality, target audience, and the emotional response the UI should evoke. Guides the agent's high-level stylistic decisions when a specific rule isn't explicitly defined.
## Overview
Minimalist fintech dashboard targeting professional traders. The design conveys
trust, precision, and clarity through a dark theme with high-contrast data
elements and restrained use of accent color.2. Colors
Defines color palettes and their semantic roles. At minimum primary must be defined.
## Colors
A dark theme with high-contrast accents for maximum readability of financial data.
- **Primary (#0A0E17):** Deep navy background evoking institutional trust.
- **Secondary (#1A1F2E):** Elevated surface color for cards and panels.
- **Accent (#3B82F6):** Electric blue used exclusively for interactive elements and CTAs.
- **Success (#10B981):** Green for positive financial indicators.
- **Danger (#EF4444):** Red for negative indicators and destructive actions.
- **Neutral (#94A3B8):** Muted slate for secondary text and borders.3. Typography
Defines typography levels with semantic roles. Most systems have 9-15 levels.
Common naming: headline-display, headline-lg, headline-md, body-lg, body-md, body-sm, label-lg, label-md, label-sm, caption.
## Typography
Uses **Inter** exclusively for a clean, modern feel. Weight variation creates hierarchy.
- **Headlines:** Semi-Bold (600) for section titles and key metrics.
- **Body:** Regular (400) at 16px for content and descriptions.
- **Labels:** Medium (500) at 12px with uppercase tracking for metadata and tags.4. Layout (also "Layout & Spacing")
Describes grid system, spacing scale, and responsive behavior.
## Layout
12-column grid on desktop, 4-column on mobile. Max content width 1280px.
8px base spacing scale with 4px half-step for micro-adjustments.
Cards use 24px internal padding. 32px gap between major sections.5. Elevation & Depth
How visual hierarchy is conveyed — shadows, tonal layers, or flat alternatives.
## Elevation & Depth
Depth through tonal layers rather than shadows. Each elevation level darkens
the background by one shade. No box-shadow used anywhere in the system.6. Shapes
Border radius and shape language for UI elements.
## Shapes
Minimal corner radius throughout. 4px for inputs and small elements,
8px for cards and modals, full (9999px) for pills and avatars.7. Components
Style guidance for component atoms. Common types: buttons, chips, lists, tooltips, checkboxes, radio buttons, input fields.
Components can have variants for states (hover, active, disabled) using related keys:
components:
button-primary:
backgroundColor: "{colors.accent}"
textColor: "#FFFFFF"
rounded: "{rounded.md}"
padding: "12px 24px"
button-primary-hover:
backgroundColor: "#2563EB"
button-primary-active:
backgroundColor: "#1D4ED8"Component property tokens: backgroundColor, textColor, typography, rounded, padding, size, height, width.
8. Do's and Don'ts
Practical guardrails.
## Do's and Don'ts
- Do use accent color only for the primary action per screen
- Do maintain WCAG AA contrast (4.5:1 for normal text, 3:1 for large text)
- Don't use more than two font weights on a single screen
- Don't mix rounded and sharp corners in the same component group
- Don't use pure black (#000) or pure white (#FFF) in dark theme — use tinted values insteadRecommended Token Names
These are commonly used but not required:
- Colors:
primary,secondary,tertiary,neutral,surface,on-surface,error - Typography:
headline-display,headline-lg,headline-md,body-lg,body-md,body-sm,label-lg,label-md,label-sm - Rounded:
none,sm,md,lg,xl,full
How to Create a DESIGN.md
When asked to create a DESIGN.md:
- Gather requirements — ask about brand personality, target audience, color preferences, and any existing brand assets
- Choose a name — pick a descriptive name for the design system
- Define tokens — start with colors and typography, then spacing, rounded, and components
- Write prose sections — explain the rationale behind each design decision
- Add Do's and Don'ts — provide practical guardrails for consistent implementation
- Validate — ensure all token references resolve, hex colors are valid, and dimensions have units
Conversion Tips
DESIGN.md tokens are compatible with:
- Tailwind — map tokens to
tailwind.config.jstheme values - Figma Variables — export/import via Figma's variable system
- tokens.json — convert to Design Token JSON spec format
- CSS Custom Properties — generate
:rootvariables from tokens
Complete Example
---
version: alpha
name: Daylight Prestige
colors:
primary: "#1A1C1E"
secondary: "#6C7278"
tertiary: "#B8422E"
neutral: "#F7F5F2"
surface: "#FFFFFF"
on-surface: "#1A1C1E"
typography:
h1:
fontFamily: Public Sans
fontSize: 48px
fontWeight: 600
lineHeight: 1.1
letterSpacing: -0.02em
h2:
fontFamily: Public Sans
fontSize: 36px
fontWeight: 600
lineHeight: 1.2
letterSpacing: -0.01em
body-md:
fontFamily: Public Sans
fontSize: 16px
fontWeight: 400
lineHeight: 1.6
label-caps:
fontFamily: Space Grotesk
fontSize: 12px
fontWeight: 500
lineHeight: 1
letterSpacing: 0.1em
spacing:
base: 16px
xs: 4px
sm: 8px
md: 16px
lg: 32px
xl: 64px
gutter: 24px
margin: 32px
rounded:
sm: 4px
md: 8px
lg: 12px
full: 9999px
components:
button-primary:
backgroundColor: "{colors.tertiary}"
textColor: "#FFFFFF"
rounded: "{rounded.md}"
padding: 12px 24px
button-primary-hover:
backgroundColor: "#9A3726"
button-secondary:
backgroundColor: "transparent"
textColor: "{colors.primary}"
rounded: "{rounded.md}"
padding: 12px 24px
---
# Daylight Prestige
## Overview
A refined editorial design system for a luxury lifestyle publication.
The aesthetic balances warmth and sophistication through high-contrast
neutrals paired with a single evocative accent. Every element is crafted
to feel intentional, readable, and quietly confident.
## Colors
The palette is rooted in high-contrast neutrals and a single, evocative accent color.
- **Primary (#1A1C1E):** A deep ink for headlines and core text — maximum
readability with a sense of permanence.
- **Secondary (#6C7278):** A sophisticated slate for borders, captions, and metadata.
- **Tertiary (#B8422E):** A vibrant earthy red — used exclusively for primary
actions and critical highlights.
- **Neutral (#F7F5F2):** A warm limestone foundation for all pages, softer than
pure white.
## Typography
Two typefaces create a clear voice hierarchy.
- **Headlines:** Public Sans Semi-Bold establishes an institutional, trustworthy voice.
- **Body:** Public Sans Regular at 16px ensures contemporary professionalism
and long-form readability.
- **Labels:** Space Grotesk in uppercase with generous tracking for technical
data, timestamps, and metadata.
## Layout
Fluid grid on mobile, fixed max-width (1200px) on desktop. 8px spacing scale
with 4px half-step for micro-adjustments. Cards use 24px internal padding
to emphasize the soft, approachable nature of the brand.
## Elevation & Depth
Depth through tonal layers — not shadows. Background uses warm off-white,
primary content sits on pure white cards. Subtle but clear visual hierarchy.
## Shapes
Architectural sharpness: 4px corner radius on interactive elements, containers,
and inputs. Modern but rigid, engineered aesthetic.
## Components
### Buttons
Primary buttons use the tertiary red on white text. Secondary buttons are
outlined with transparent backgrounds. Both share 8px radius and consistent
horizontal padding.
### Cards
White surface on neutral background. 12px radius. 24px internal padding.
No border — elevation is achieved through color contrast alone.
## Do's and Don'ts
- Do use the tertiary color only for the single most important action per screen
- Do maintain WCAG AA contrast ratios (4.5:1 for normal text)
- Don't mix rounded and sharp corners in the same view
- Don't use more than two font weights on a single screen
- Don't introduce colors outside the defined paletteAuto-Loading DESIGN.md
Claude Code reads CLAUDE.md automatically at the start of every session, but does not automatically read DESIGN.md. To ensure the agent always applies the design system, add an instruction in the project's CLAUDE.md:
# CLAUDE.md
Always read and follow DESIGN.md before making any UI or styling changes.Without this, DESIGN.md is only read when the user explicitly asks or when the design-md skill is triggered.
Spec Reference
Full specification: https://github.com/google-labs-code/design.md/blob/main/docs/spec.md
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.

