DESIGN.md is a structured markdown file that defines your project's brand spec — tokens (colors, typography, spacing, radius), voice, narrative, principles, personas, states, and motion. AI coding agents (Claude Code, Codex, OpenCode, Cursor) read it as authoritative context before generating any UI, so the output looks like your brand instead of generic 'modern minimalist' slop.

How does oh-my-design work?

Run `npx oh-my-design-cli install-skills` once in your project. It installs 18 skills (core flow + live-capture + asset + the v0.2 agent layer: orchestrator, kr-writer, locale-adapter, designer-review, final-qa, codex-image), 16 sub-agents (master orchestrator + 15 specialists), 4 hooks, and 440 reference DESIGN.md files. After restarting your AI coding agent, you just talk in natural language — skills route to the right sub-agents automatically.

Does it call any AI provider during install?

No. The install is a pure markdown copy — zero API calls, zero data leaves your machine. Your AI coding agent (Claude Code, Codex, OpenCode, or Cursor) is the inference layer; install just teaches it where to look.

Which AI coding agents are supported?

Claude Code, Codex, OpenCode, and Cursor — Cursor has a dedicated install channel (--agent cursor) that writes the .cursor/rules shim plus the shared reference catalog. The skill markdown files are agent-agnostic; hooks ship for Claude Code specifically.

What is the design harness?

The omd-harness skill runs a 10-phase design pipeline (Discovery → Research → IA → Wireframes → Design system → Components → Asset sourcing → Microcopy → Validation → Handoff). It dispatches sub-agents in parallel where independent, asks 3 mandatory user checkpoints, and emits a v0/Cursor-ready package. Trigger it by saying things like 'design the entire onboarding from scratch' or '/omd-harness '.

Yes — MIT licensed, open source, no signup, no API key, no paid tier. The references in the bundle belong to their respective companies and are reproduced for educational reference only.

Karrot reference

Download .md

Verified reference evolution

Karrot: previous snapshot → Verified v2

Karrot uses warm orange accents and restrained chrome to keep neighborhood content and human relationships dominant. The reference treats SEED v2 as the canonical product-system source while preserving the public marketing site as a separate source for its font stack and CTA geometry.

Evidence boundary: SEED product primary #ff6f0f and marketing CTA #ff6600 are both valid, but neither replaces the other outside its documented surface.

Checked: 2026-07-11
Claims: 63/63
Sources: 7
Surfaces: 3
Conflicts: 0

Recorded changes

Only repository-recorded changes are shown. Unknown history remains absent.

tokens.colors.primary

Previous snapshot

#ff6600 universal primary

Verified v2

#ff6f0f SEED product primary

The current product token now comes from official SEED v2; #ff6600 remains only as a measured marketing CTA.

tokens.components

Previous snapshot

Generic listing cards, inputs, and destructive buttons

Verified v2

Official SEED component contracts and measured marketing controls

Plausible marketplace UI was removed unless an official contract or live surface supported it.

Use the current verified reference

Open the builder with Karrot selected, then preview or export the canonical DESIGN.md.

Open in builder