Agentic Design System Defaults
The 9 templates I install on every agentic design system. One zip, the whole installable baseline. CLAUDE.md, governance, MCP, token schema, component intent map, and four audit skills.
What this is
The 9 templates I install on every agentic design system, bundled into one zip with an install order. This is the convenience version of nine pages on aidesign.guide. One download instead of nine.
Drop the files into your project, replace placeholders with your own conventions, and Claude Code understands your design system from the first prompt.
What you will need
Master plan. Yearly only. Bundled because the install order matters.
Any folder with components, tokens, or both. Existing or new.
The bundle is built around Claude Code's CLAUDE.md, MCP, and skills systems.
Realistic time to drop in the kit, edit names, and run your first audit.
Download
The full bundle is one zip with all 9 templates plus a README that explains the install order. About 20 KB.
Download the defaults (.zip)
What’s inside
- README.md
- 01-CLAUDE.md
- 02-governance-rules.md
- 03-mcp-setup.json
- 04-token-schema.json
- 05-component-intent-map.json
- 06-anti-pattern-check-SKILL.md
- 07-taste-audit-scorecard.md
- 08-motion-audit-SKILL.md
- 09-multi-lens-review/ 4 review skills
Why bundled
Every file in this bundle has its own template page on aidesign.guide. The reason to ship them together is the install order. CLAUDE.md and the token schema have to land first or the rest of the kit has no rules to lean on. MCP setup goes next because the audit skills lean on Figma and GitHub access. The four review skills install last because they reference the rules established in the first five files.
You can install pieces individually from the per-template pages. The bundle is the convenience: one download, the whole installable baseline, in the order I would run it myself.
Install order
- CLAUDE.md and token schema first. Project-level rules. Without them, the rest of the kit has no context.
- MCP setup. Connect Figma, GitHub, Playwright. Restart Claude Code.
- Component intent map. Now Claude knows what each component is for, not just how it looks.
- Governance rules. Lock in what AI can do without asking.
- Skills. Anti-pattern check, motion audit, multi-lens review. They depend on the rules above.
After install
Each file expects customization:
- Replace placeholders in
CLAUDE.md(project name, framework, token format, file paths) - Add your real API tokens to
.mcp.json(Figma personal access token, GitHub fine-grained token) - Adjust
token-schema.jsonto match your category and intent vocabulary - Edit
component-intent-map.jsonso the components match your library - Tune audit rubrics if your project has stricter or looser rules
Full instructions inside the bundle’s README.md.
Each template, on its own page
If you want to read the full rationale, see customization patterns, or copy-paste the content without downloading, every file in this bundle has its own page.
Updates
These templates evolve with the practice. When the bundle updates, the date on each individual template page reflects the latest version. Re-download whenever you want the current snapshot.
The guides alone saved me a full day of work every sprint.
- All guides, prompts, and templates
- Starter kits and templates
- New content every week
- Priority support