Identity Forge packs fonts, colors, semantic tokens, and a DESIGN.md into one curated kit that Claude Code, Cursor, and v0 read every session. Pick a kit below and see it on real surfaces before your agent builds with it.
npx identityforge@latest install --client claude-codenpx identityforge@latest loginUse Identity Forge to pick a theme that fits this product, apply it, and follow the DESIGN.md.Free kits work out of the box. Get an API key for the full library and your plan quota.
Works with every AI builder & agent
Choose a kit
65 themes, each with its own fonts, colors, and spacing
Landing page: Full marketing page — hero, social proof, features, a metrics/graph section, and CTA — as alternating full-bleed bands in the kit's captured surfaces. Scroll to explore.
Generated live · not templates
Every screen below was built by an AI coding agent from a single Identity Forge kit — its DESIGN.md and design tokens, nothing else. No hand-coding, no templates. Filter by type, scroll any card to walk through its page, click to open the real thing.
Fixed combinations of fonts, colors, tokens, and spacing. Each kit is a complete visual system ready for AI coding agents.
Three failure modes that happen before you realize it.
Your agent picks a slightly different blue every session. After ten sprints, your UI has fifteen grays, four primary shades, and a button that matches nothing.
You paste the same font names, token values, and usage notes into every new session. It works once. The next session starts from scratch.
"Make it look premium" means nothing to an agent. Without specific token names and component rules, every sprint reinvents the system.
It follows the font rules, color roles, and component conventions in every session without being told twice. One export. Permanent visual consistency.
From visual direction to agent-readable implementation files in one workflow.
Tell us what the product, market, or agent-built interface should feel like
Start from a curated visual system with fonts, colors, tokens, and usage rules
See the kit on realistic UI surfaces before asking an agent to build with it
Choose a name and domain when the kit needs to become a complete brand
Copy DESIGN.md, shadcn variables, Tailwind config, tokens JSON, or API links
Stop making every AI session rediscover visual direction. Give it tokens, examples, and constraints it can actually use.
Curated font, color, radius, spacing, and semantic-token combinations for agents to apply consistently.
Generate DESIGN.md, shadcn CSS variables, Tailwind config, DTCG tokens, and registry JSON from one source.
Every kit maps raw colors to background, foreground, primary, accent, status, chart, border, and ring roles.
Heading, body, and mono font choices include Next.js font setup, CSS variables, weights, and usage rules.
Use public API routes or shadcn-compatible registry endpoints to bring kits into agent workflows.
Keep the existing naming and domain pipeline, then use the selected name and domain in previews and exports.
A single source of truth fans out into every format the modern AI stack consumes, no manual translation, no hex drift.
Choose a design kit
Colors, type, radius, spacing, already harmonized.
Your agent ships on-brand
Consistent across every screen and session.
Different workflows. Same result: a UI that holds together.
You ship with Claude Code, Cursor, or v0. Your UI should look intentional, not accidental. One kit sets the rules. Your agent follows them every session.
Browse kits →Start from a real token system, not a blank globals.css. Every kit ships ready for shadcn, Tailwind, and DTCG pipelines. No inventing, no guessing.
Open API docs →Your MVP needs to look like a real product. Pick a kit, export DESIGN.md, hand it to your agent. Done in five minutes.
Get a kit free →Stop converting tokens by hand. Export DESIGN.md, CSS variables, Tailwind themes, or shadcn registry JSON, all from the same source.
# Ambient Sage — DESIGN.md ## Fonts - Heading: Plus Jakarta Sans (--font-heading) - Body: Plus Jakarta Sans (--font-sans) - Mono: JetBrains Mono (--font-mono) ## Agent rules - Separate panels with tonal surface shifts, not shadows. - Reserve yellow (#FEE951) for actions and focus.
:root {
--background: 72 9% 10%;
--foreground: 68 13% 88%;
--primary: 53 99% 66%;
--accent: 52 89% 68%;
--radius: 1.25rem;
}npx shadcn add \ https://identityforge.io/r/ambient-sage.json
@theme {
--color-background: oklch(20% 0.02 120);
--color-primary: oklch(92% 0.18 100);
--color-accent: oklch(90% 0.15 100);
--font-heading: "Plus Jakarta Sans";
}DESIGN.md is a structured markdown file that gives your coding agent everything it needs: token names, font roles, usage rules, and component constraints.
# Ambient Sage — DESIGN.md
## Purpose
Calm, warm product system for focused tools,
wellness products, and thoughtful dashboards.
## Color tokens (dark)
| Token | Value | Role |
|---------------|---------|-------------------|
| --background | #1A1C17 | Page background |
| --primary | #FEE951 | Actions, focus |
| --accent | #F7E464 | Quiet emphasis |
| --destructive | #CC3333 | Errors, warnings |
## Typography
- Heading: Plus Jakarta Sans (warm clarity)
- Body: Plus Jakarta Sans (readable at all sizes)
- Mono: JetBrains Mono (code, IDs, values)
## Agent rules
1. Use tonal surface shifts instead of card shadows.
2. Reserve yellow for actions and focus states.
3. Use generous rounding consistently across controls.
4. Keep display data large, calm, and easy to scan.
Colors are not just palettes; they are roles. Every kit maps background, foreground, primary, accent, status, chart, border, and ring to specific hex values your agent uses by name.
Ambient Sage, dark mode
Every kit defines three font roles. Agents reference them by CSS variable, never by name, never by guessing.
Ship fast.
Plus Jakarta Sans· 600 · monospaceA focused system for tools that inspect, execute, and explain complex workflows.
Plus Jakarta Sans· 400-600 · sans-serifconst kit = await getKit("ambient-sage")
JetBrains Mono· 400-500 · monospaceEvery session your agent builds UI without a system is a session that drifts. A kit fixes it permanently.
Pick a kit. Export DESIGN.md. Your agent has a complete token system, font rules, and component constraints — in one file.
Works this session. Gone next time. You re-explain fonts, colors, and rules in every new chat.
Generic look. No personality. Every project using shadcn defaults looks the same. Agents drift to random choices.
Takes days. Breaks with every refactor. Hard to share with an agent in a prompt.
One feature set, three ways to pay. Every plan unlocks the full kit catalogue, all export formats and the brand API. Displayed prices include applicable tax.
Monthly
Flexible, cancel anytime
$9/mo
Get MonthlyYearly
Just $4.50/mo, billed yearly
$54/yr$108
Get YearlyLifetime
Pay once, yours forever
$149once
Get LifetimeFree, browse every kit and export the basics. 20 AI generations / month.
Start freeEverything you need to know about Identity Forge design kits.
Start free. Upgrade when you need the full catalogue.
Browse kits free