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.

Kakao reference

Download .md

Verified reference evolution

Kakao: previous snapshot → Verified v2

Kakao’s recognizable yellow and speech-bubble identity spans multiple services, but its public surfaces do not form one transferable UI kit. The reference distinguishes Kakao corporate typography, the regulated Kakao Login integration, and Pretendard-based developer-documentation chrome.

Evidence boundary: Corporate marketing yellow, Kakao Login yellow, and developer-documentation styles remain surface-local even when they look visually related.

Checked: 2026-07-11
Claims: 102/102
Sources: 4
Surfaces: 4
Conflicts: 0

Recorded changes

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

tokens.colors.primary

Previous snapshot

#fee500 as a universal Kakao primary

Verified v2

No universal product primary

The same company identity cannot promote a login-integration color into every Kakao product surface.

tokens.components

Previous snapshot

Generic chat inputs, cards, and destructive controls

Verified v2

Observed corporate controls and official Kakao Login only

Unverified Kakao-like application components were removed while separately sourced public controls were preserved.

Use the current verified reference

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

Open in builder