A machine-readable system for consistent, scalable marketing production using AI.
This is not just a design system.
It is a full operating system for how content gets created, structured, and validated across outputs like decks, case studies, reports, and one-pagers.
Turn this:
"Create a marketing case study"
Into this:
Use DESIGN.md, BRAND.md, VOICE.md, and VOCABULARY.md to generate a structured case study with clear hierarchy, consistent tone, and defined sections (Problem, Solution, Results).colors:
primary: "#2665fd"
surface: "#0b1326"
on-surface: "#dae2fd"
spacing:
base: 8
scale: [4, 8, 16, 24]Design is no longer abstract.
It becomes a system AI can read and execute.
Most design systems stop at UI.
They define tokens, colors, and components.
That works for product teams.
It breaks for marketing.
Marketing outputs are:
- Unstructured
- Variable in format
- Dependent on narrative, layout, and tone
DesignOS solves this by standardizing how content is built, not just how it looks.
AI needs machine-readable systems to produce consistent results.
DesignOS provides that system.
It defines:
- What to say
- How to say it
- How it should look
- How it should be structured
Before anything ships.
Input → System → Output
DESIGN.md → Layout and hierarchy
VOICE.md → Tone and clarity
VOCABULARY.md → Terminology
BRAND.md → Identity
= Structured, consistent outputs
-
Copy the system files into your project:
- DESIGN.md
- BRAND.md
- VOICE.md
- VOCABULARY.md
-
Paste into your AI tool
-
Use this prompt:
Use this DesignOS system to generate a landing page for a SaaS product. Follow the structure, tone, and design rules defined in the files.Use this to generate consistent outputs with DesignOS.
You are operating using DesignOS v1.0.
You must follow all system files strictly:
- DESIGN.md → controls layout, hierarchy, structure
- BRAND.md → controls identity, visual consistency, constraints
- VOICE.md → controls tone, messaging, sentence structure
- VOCABULARY.md → controls terminology and language enforcement
- DESIGN_OS.md → governs output structure, validation, and system logic
---
## Objective
Generate a high-quality output that is:
- Structured
- Consistent
- Clear
- Scalable
---
## Execution Rules
You MUST:
1. Follow the correct document structure based on output type
2. Apply clear hierarchy (sections, flow, readability)
3. Maintain consistent tone (clear, direct, human)
4. Use only approved vocabulary
5. Avoid banned or vague language
6. Ensure output is easy to scan and understand
---
## Output Structure
- Deck → Cover, Problem, Solution, Results, CTA
- Case Study → Problem, Approach, Solution, Results
- Report → Summary, Insights, Data, Recommendations
- Landing Page → Hero, Problem, Solution, Features, CTA
---
## Validation (MANDATORY)
Before finalizing, check:
- Structure is complete
- Tone is consistent
- Vocabulary is compliant
- Layout is clear
If any rule fails:
→ Regenerate that section
---
## Output Requirements
- Clean formatting
- Clear sections
- No unnecessary text
- No explanation of the system
Only return the final output.
## Input
Now generate:
[INSERT YOUR REQUEST HERE]- DESIGN.md - Visual system (layout, components, hierarchy)
- BRAND.md - Brand identity and principles
- VOICE.md - Tone and communication style
- VOCABULARY.md - Approved language and naming rules
- DESIGN_OS.md - Governing system (rules, logic, orchestration)
Defines the visual system.
- Layout rules
- Component behavior
- Spacing and hierarchy
- Interaction patterns
Not token-based - built for real outputs.
layout:
grid: 12
spacing: 8
components:
button:
radius: 8px
height: 44px
typography:
heading: 28px
body: 16pxDefines what the brand stands for.
- Visual identity
- Color usage
- Design principles
brand:
primary: "#000000"
secondary: "#FFFFFF"
accent: "#4F46E5"
principles:
- clarity
- consistency
- simplicityDefines how the brand communicates.
- Tone
- Writing style
- Messaging structure
tone:
style: direct
voice: confident
rules:
- short sentences
- no jargon
- active voiceDefines what language is allowed.
- Approved terms
- Banned terms
- Naming conventions
- Microcopy rules
approved:
- AI-powered
- workflow
- system
banned:
- revolutionary
- next-gen
- seamless
buttons:
maxWords: 2The brain of the system.
- Governs all files
- Defines how outputs are generated
- Enforces consistency across assets
- Connects design, brand, and language into one system
Traditional systems:
- Focus on UI
- Stop at tokens
- Assume human execution
DesignOS:
- Built for AI + human workflows
- Covers full content production
- Applies to marketing outputs, not just interfaces
- Includes validation logic before publishing
Different rules depending on output type:
Encodes how each asset is built step-by-step.
Design becomes executable structure.
Outputs are checked before shipping:
- Layout consistency
- Tone alignment
- Vocabulary compliance
DesignOS v1.0
This version defines the core system:
- DESIGN.md
- BRAND.md
- VOICE.md
- VOCABULARY.md
- DESIGN_OS.md
Future versions will expand validation, automation, and system integrations.
- Marketing teams using AI
- Agencies scaling content production
- Founders building consistent brand outputs
- Designers bridging UI and marketing systems
- https://getdesign.md/ - Official DESIGN.md overview and examples
- https://github.com - Search "DESIGN.md" to explore real implementations
- https://designmd.ai/ - AI-powered tools and workflows built around DESIGN.md
- https://designmd.app/en/ - Interactive platform for exploring and using DESIGN.md
- https://chromewebstore.google.com/detail/designmd-style-extractor/ogpdnchdjiibhobphelbbkemnnemkfma?pli=1 - Chrome extension to extract styles into DESIGN.md format
- Clone or download the repo
- Add files to your project
- Use them as input context for AI tools (ChatGPT, Claude, etc.)
- Generate outputs with structured consistency
If content is not structured, it cannot scale.
DesignOS introduces constraints so AI can produce consistent, high-quality outputs.
This system is evolving.
Feel free to fork, adapt, and extend based on your workflows.