To make an agent use DESIGN.md, point its persistent-context mechanism at the file. The pattern is the same everywhere: tell the agent to read DESIGN.md for UI work.
Reference DESIGN.md from your CLAUDE.md:
## Design
This project has a DESIGN.md defining the visual identity.
Before generating or modifying any UI, read DESIGN.md and
follow its tokens and rationale. Use the accent color only
as the rationale specifies.
Use a rules file to inject DESIGN.md into every UI generation, so the design context is present whenever the agent produces interface code.
Every agent has a persistent-context mechanism; you route it to your design file.
Ask the agent to generate a component and inspect the result:
The first generation usually reveals a gap in your prose. Fill it, and the fix is permanent.
Because DESIGN.md is an open format, the same file serves Claude Code, Cursor, Kiro and Windsurf at once - one design source of truth, no per-tool drift.
Where do DESIGN.md files come from? Write one by hand, generate a draft with an agent, or export from Google Stitch.
Does it work across tools? Yes - one file, read by each tool's own mechanism.
Wiring in DESIGN.md is always the same move: tell the agent's context mechanism to read the design file for UI work.
Free starter: The format, a complete annotated example, and the core idea are on a free cheat sheet: DESIGN.md Quick-Start Cheat Sheet
Go deeper: The full guide covers the entire format — the token schema, the CLI in depth, accessibility, Tailwind and DTCG export, agent integration, and a complete walkthrough: DESIGN.md: The Complete Guide to Design Systems for AI Agents
Which agent are you wiring DESIGN.md into first? Curious which tools people are using for UI work these days.