Give your coding agent a design system
Give Claude Code, Cursor, v0, Lovable, Bolt, and Windsurf a real, consistent design system installed via MCP, the CLI, or the shadcn registry.
18 guides in this topic.
Design systems for AI coding agents
An AI agent with no design system invents one per prompt, and it invents the same one everybody else gets. What to give it instead, what that file has to contain to actually work, and how to install it in each major tool.
Updated 2026-07-27
How to get polished results from AI design kits
A design kit is a starting point. What makes it stick is enforcing tokens in every component, building on solid primitives, finding visual direction with image gen, and generating variations instead of accepting the first attempt.
Updated 2026-08-10
Give Claude Code a design system
Install a design system into Claude Code with one command: an MCP server lets the agent browse kits, apply tokens, and follow a real DESIGN.md as it builds.
Updated 2026-08-03
Claude Code's frontend-design plugin: install it, what it does, what it misses
Two commands install Anthropic's frontend-design plugin, and it makes one screen look good. It cannot make the twentieth screen match the first, because it carries taste and not values. Here is the install, the gap, and how to close it.
Updated 2026-08-04
Claude Code skills, explained: what loads, when it fires, and how to write one
A skill is a folder with a SKILL.md that Claude Code loads only when your task matches its description. That one sentence explains why most installed skills never do anything. Here is the mechanism, the file format, and a worked design skill.
Updated 2026-08-04
Codex skills: where they live, how $ invocation works, and how to write one
Codex discovers SKILL.md folders in five locations, loads them by description match or an explicit $, and shares the format with Claude Code and Cursor. Here is the anatomy, the discovery order, and a design skill you can adapt.
Updated 2026-08-04
Give GitHub Copilot a design system
Copilot reads instructions files nobody fills with design decisions, which is why its UI output defaults to generic. Here is the setup: copilot-instructions.md, scoped .instructions.md files, real tokens, and a DESIGN.md they point at.
Updated 2026-08-04
Give Gemini CLI a design system
Gemini CLI concatenates every GEMINI.md in its hierarchy into each prompt, which makes it unusually easy to wire a design system in: one import line and the contract loads on every request. Here is the setup and the file it imports.
Updated 2026-08-04
Give Cursor a design system
Add Identity Forge's MCP server to Cursor: the Agent picks a design kit, writes its tokens and DESIGN.md into your project, and keeps its screens consistent.
Updated 2026-08-03
Give Windsurf a design system
Connect Identity Forge to Windsurf's Cascade agent with a small MCP config, or use the CLI and shadcn registry, so every screen follows one design system.
Updated 2026-08-03
Give v0 a design system
Make v0 build on-brand UI: hand it a design kit as a shadcn registry item plus a DESIGN.md brief, so generations use your tokens, not the default look.
Updated 2026-08-03
Lovable prompts for design: what works, what drifts, and why
Most Lovable prompt lists collect one-liners. Design doesn't survive one-liners. Here is the anatomy of a design prompt that holds across sessions, with paste-ready examples.
Updated 2026-08-03
Give Lovable a design system
Make Lovable build on-brand: put a kit's DESIGN.md in project Knowledge and apply its tokens through the shadcn registry in the connected repo.
Updated 2026-08-03
Give Bolt a design system
Bolt's built-in design systems need a paid Team plan to add your own. Here is what that feature compiles from, and the setup that works on any plan using Bolt's real in-browser terminal.
Updated 2026-07-27
Cursor rules for a design system: why one file stops working
The standard advice is to write a design.mdc rule and you are done. It works for about three weeks. Here is why a design system does not fit in one rules file, how to split it by when each rule needs to be true, and what to put in each piece.
Updated 2026-07-27
Design system MCP servers: what they fix and what they don't
An MCP server lets an agent query your design system instead of guessing at it. That solves wrong prop names and stale imports. It does not solve an agent that has no idea what your product should look like, and those are different problems with different fixes.
Updated 2026-07-27
AI design tools for developers, sorted by what they replace
Most roundups list twenty tools that do different jobs as if they were competing. Here they are grouped by the problem each one solves, with the finding that matters: not one of them produces a design system, and all of them assume you already have one.
Updated 2026-07-27
Framer design system: styles vs DESIGN.md
Where design decisions live in a Framer project, how DESIGN.md relates to shared styles, components, and overrides, and how to verify changes on a branch.
Updated 2026-08-03