design-system
Skill56 starsChanged 8 months agoMITView on GitHub
DESIGN.md integration for Forge — ensures visual consistency across all UI tasks through standardized design specifications
193 other projects use a version of this.
Adopted by
Most recently taken up by
- Rugved1652/skillstheir own version, first seen Nov 16, 2026
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- irank786/Claude-skillstheir own version, first seen Nov 16, 2026
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- AndresArreguy/ecc-pi-porttheir own version, first seen Nov 16, 2026
- Vujavujavuja/Stillmotion-onbrandtheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-engine, team-level 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.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 14 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 13 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 12 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 12 projects that use this
- +6 more from lilangMax
- +2 more from CoralGame
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- nextlevelbuilder/ui-ux-pro-max-skill★ 150ksame name
- getsentry/sentry★ 46ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- ethereum/ethereum-org-website★ 6ksame name
- langwatch/langwatch★ 5ksame name
- joye61/pic-smaller★ 2.9ksame name
- daveebbelaar/bama★ 1.7ksame name
- reatom/reatom★ 1.4ksame name
- microsoft/power-platform-skills★ 1.2ksame name
183 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backpropagationSkill
- brainstormingSkill
- caveman-internalSkill
- collaboratingSkill
- executingSkill
- graphify-integrationSkill
- karpathy-guardrailsSkill
- planningSkill
- reviewingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 7 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 176 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
If found, load it and reference it throughout the workflow.
- Very specific: line 39
When /forge brainstorm runs for a project with UI components:
- Very specific: line 52
Write to DESIGN.md in the project root
- Very specific: line 55
Include design context in specs: When writing spec files, add a design field in frontmatter:
- Very specific: line 66
When /forge plan encounters specs with UI tasks:
- Very specific: line 81
When forge-executor handles a task tagged with design::
- Distinctive: line 90
Use only colors defined in the palette (no ad-hoc hex values)
- Distinctive: line 91
Follow the typography hierarchy (no custom font sizes)
- Very specific: line 101
When forge-reviewer reviews UI tasks with design context:
- Distinctive: line 104
Add a Design Compliance pass: after spec compliance:
- Distinctive: line 111
No ad-hoc design values that contradict the design system
- Distinctive: line 131
When generating a new DESIGN.md, use this structure:
- Distinctive: line 203
When no DESIGN.md exists:
- Very specific: line 209
No Forge workflow should ever fail because DESIGN.md is absent.
“Common” is measured: kept by at least 6 in 10 of the 176 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 System Skill
This skill integrates DESIGN.md-based design specifications into the Forge workflow. When a project has a DESIGN.md file, all UI-related tasks automatically inherit design constraints, ensuring brand consistency across parallel agent execution.
What is DESIGN.md?
DESIGN.md is a standardized markdown format for design specifications that AI agents can read and follow. It contains:
- Visual Theme and Atmosphere -- brand philosophy and design mood
- Color Palette -- semantic color definitions (Primary, Error, Surface, etc.) with hex values
- Typography Hierarchy -- font families, weights, sizes for H1-H6, body, caption
- Component Styling -- button specs, card styling, input borders, border radius, shadows
- Layout Principles and Spacing -- spacing scale (base unit), margin/padding rules, grid conventions
- Depth and Elevation Systems -- shadow definitions, z-index hierarchies
- Design Guardrails and Anti-Patterns -- what NOT to do, brand identity boundaries
- Responsive Behavior Parameters -- mobile/tablet/desktop breakpoints, scaling rules
- Agent Prompt Guide -- quick reference for AI agents to maintain consistency
Detection
At the start of brainstorming or planning, check for an existing DESIGN.md:
# Check common locations
ls DESIGN.md design.md docs/DESIGN.md 2>/dev/nullIf found, load it and reference it throughout the workflow.
Integration with Forge Phases
Brainstorming Phase
When /forge brainstorm runs for a project with UI components:
- Check for DESIGN.md -- if it exists, reference it during spec generation
- If no DESIGN.md exists, ask the user during the Q&A phase:
Does this project have a design system or brand guidelines? A) Yes, I have a DESIGN.md file (specify path) B) I want to base it on an existing brand (specify which -- e.g., Stripe, Linear, Claude) C) No specific design requirements -- use sensible defaults D) I'll provide design specs later
- If option B, generate a DESIGN.md by referencing the awesome-design-md catalog:
- Extract the relevant design system's color palette, typography, and component specs
- Adapt it for the user's project
- Write to
DESIGN.mdin the project root - Include it in the spec's context
- Include design context in specs: When writing spec files, add a
designfield in frontmatter:--- domain: auth status: approved design: DESIGN.md ---
Planning Phase
When /forge plan encounters specs with UI tasks:
- Load DESIGN.md and extract key constraints (color palette, typography, spacing scale)
- Tag UI tasks with design context in the frontier:
- [T005] Login form component | est: ~6k tokens | design: DESIGN.md | depends: T003 - Group UI tasks by design community: Components sharing design patterns (forms, cards, navigation) should be in the same tier when possible to ensure visual consistency
- Add design verification task at the end of UI-heavy specs (depth >= standard):
- [T012] Design consistency verification | est: ~4k tokens | depends: T005, T007, T009
Execution Phase
When forge-executor handles a task tagged with design::
- Load DESIGN.md at task start, alongside the spec and frontier
- Extract relevant design tokens for the task:
- Color values for the component being built
- Typography specs for text elements
- Spacing values for layout
- Component styling (border-radius, shadows, etc.)
- Apply design constraints during implementation:
- Use only colors defined in the palette (no ad-hoc hex values)
- Follow the typography hierarchy (no custom font sizes)
- Apply the spacing scale (no magic pixel values)
- Match component styling specs (border-radius, shadows)
- Document design decisions in the checkpoint context_bundle:
{"design_tokens": "primary=#1A73E8, radius=8px, spacing=8px-base"}
Review Phase
When forge-reviewer reviews UI tasks with design context:
- Load DESIGN.md alongside the spec
Add a Design Compliance pass after spec compliance:
Design Compliance Checks:
- Colors used in the implementation exist in the DESIGN.md palette
- Font families and sizes match the typography hierarchy
- Spacing values follow the defined scale (or multiples of the base unit)
- Component styling matches specs (border-radius, shadows, elevation)
- No ad-hoc design values that contradict the design system
- Responsive breakpoints match DESIGN.md if specified
- Flag design violations:
- IMPORTANT: Color not in palette (e.g., used #FF0000 instead of defined Error color)
- IMPORTANT: Font size not in typography scale
- MINOR: Spacing value not a multiple of base unit
- MINOR: Missing responsive behavior for a defined breakpoint
- Output format:
DESIGN COMPLIANCE: - [x] Colors: All colors from DESIGN.md palette - [ ] Typography: H2 uses 28px, DESIGN.md specifies 24px - [x] Spacing: All values multiples of 8px base - [x] Components: Border radius matches spec (8px)
DESIGN.md Template
When generating a new DESIGN.md, use this structure:
# DESIGN.md
## Visual Theme and Atmosphere
{Brand philosophy, mood, design direction}
## Color Palette
| Token | Value | Usage |
|-------|-------|-------|
| Primary | #XXXXXX | Main interactive elements, CTAs |
| Primary Dark | #XXXXXX | Hover states, active elements |
| Secondary | #XXXXXX | Supporting UI, secondary actions |
| Accent | #XXXXXX | Highlights, badges, notifications |
| Background | #XXXXXX | Page background |
| Surface | #XXXXXX | Card/panel background |
| Error | #XXXXXX | Error states, destructive actions |
| Success | #XXXXXX | Success states, confirmations |
| Warning | #XXXXXX | Warning states |
| Text Primary | #XXXXXX | Main body text |
| Text Secondary | #XXXXXX | Supporting text, labels |
| Border | #XXXXXX | Dividers, input borders |
## Typography
| Level | Font | Size | Weight | Line Height |
|-------|------|------|--------|-------------|
| H1 | {font} | {size}px | 700 | {lh} |
| H2 | {font} | {size}px | 600 | {lh} |
| H3 | {font} | {size}px | 600 | {lh} |
| Body | {font} | {size}px | 400 | {lh} |
| Caption | {font} | {size}px | 400 | {lh} |
| Code | {mono font} | {size}px | 400 | {lh} |
## Component Styling
- **Button border-radius**: {N}px
- **Card border-radius**: {N}px
- **Input border-radius**: {N}px
- **Card shadow**: {shadow definition}
- **Elevated shadow**: {shadow definition}
## Spacing Scale
- **Base unit**: {N}px
- **Scale**: {N/2}, {N}, {N*1.5}, {N*2}, {N*3}, {N*4}, {N*6}, {N*8}
## Layout
- **Max content width**: {N}px
- **Grid columns**: {N}
- **Gutter**: {N}px
## Responsive Breakpoints
| Name | Min Width | Behavior |
|------|-----------|----------|
| Mobile | 0px | Single column, stacked layout |
| Tablet | {N}px | {behavior} |
| Desktop | {N}px | Full layout |
## Design Guardrails
- {Rule 1: what to avoid}
- {Rule 2: what to maintain}
- {Rule 3: brand boundaries}
## Agent Prompt Guide
When implementing UI for this project:
- Use only colors from the palette above
- Follow the typography hierarchy exactly
- Use spacing values from the scale (multiples of {base}px)
- Apply component styling specs for all interactive elementsGraceful Degradation
When no DESIGN.md exists:
- Brainstorming proceeds normally, optionally asking about design requirements
- Planning proceeds without design tags on tasks
- Execution proceeds without design constraints
- Review skips the design compliance pass
No Forge workflow should ever fail because DESIGN.md is absent.
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.

