Skip to content
Menu: Overview

The DESIGN.md archive and oh-my-design-cli

oh-my-design has two parts. The archive holds 622 DESIGN.md files written from real companies' products. oh-my-design-cli installs skills that make your coding agent read a DESIGN.md before it touches your UI.

The archive and the CLI

The archive

Each DESIGN.md describes one company's colors, type, spacing, components and voice; verified files also note where each value was read. Open one, then copy it, download it, or fetch the raw file from oh-my-design.kr/<id>/design.md. You don't need the CLI for any of this.

Open the archive

oh-my-design-cli

One command adds the 33-skill bundle (12 public skills and the internal ones they call), 20 specialist agents and an offline copy of the archive to Claude Code, Codex, OpenCode or Cursor, as far as each tool supports them. The skills set up your project's DESIGN.md and follow it on every UI change.

Install the CLI

Install

Run this at your project root. It finds the coding agents you use and asks which ones to set up.

npx oh-my-design-cli@latest
npx oh-my-design-cli@latest doctor

Then restart the agent, run doctor once, and describe the screen you want. No daemon, API key or MCP server is involved.

What to ask for

You don't need skill names. Say what to build and what must not change; the installed skills pick the workflow.

Create a design system

Turn a product brief and one verified_v2 reference into a DESIGN.md your project owns. Facts nobody verified stay out.

Set up a calm, trustworthy design system for our family finance app. Use Toss as a reference, but keep our existing logo and copy.
Result
DESIGN.md, agent instruction files, the tokens that differ from the reference, and a first screen you approved.

Build a complete screen

Research, IA, wireframes, components, copy, accessibility and validation run as one workflow that stops for your approval.

Design and implement the onboarding for this app. Keep the current stack and use our DESIGN.md as the source of truth.
Result
A working screen with its states, validation notes, and handoff files in the repository.

Improve an existing UI

Audit what is already there, keep the product's behavior, and fix hierarchy, rhythm, accessibility and generic AI patterns.

Improve the pricing page without changing its URLs or field names. Explain the high-impact fixes and verify the result.
Result
Focused code changes, the reasoning behind them, and the checks that ran.

How far to trust a file

Every DESIGN.md carries a quality tier. 453 verified_v2 files were checked against the live product and give a source for each value, so use these for anything public. 88 partial files are verified in places, and 81 legacy snapshots predate the current format. A value nobody could verify is left out rather than filled with a plausible default.

Next steps