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.

NAVER reference

Download .md

Verified reference evolution

NAVER: previous snapshot → Verified v2

NAVER’s official green connects a dense family of search and discovery services, but the company does not expose one public product design system for every surface. The reference therefore separates portal-home controls, search-results patterns, and the NAVER Corp brand-resource page.

Evidence boundary: NAVER Green is an identity constant; portal/search System-first typography and corporate-page InterVariable remain separate surface observations.

Checked: 2026-07-11
Claims: 101/101
Sources: 5
Surfaces: 3
Conflicts: 0

Recorded changes

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

tokens.colors.primary

Previous snapshot

#03c75a as a universal UI primary

Verified v2

#03c75a as official brand identity

The official color remains, but it no longer authorizes generic buttons, cards, or inputs across NAVER services.

tokens.components.search

Previous snapshot

Generic 56px green search input

Verified v2

Measured portal search input and submit controls

The branded search assembly now follows live portal geometry and keeps unobserved states absent.

Use the current verified reference

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

Open in builder