For AI agents & the developers using them
Give what you build a real design system.
Identity Forge is a branding pipeline for the agentic era. It hands a coding agent or web builder a complete, implementation-ready brand system. It is not a color-plus-font pair or vague inspiration. The result has a coherent identity instead of generic defaults.
What Identity Forge is
The unit of value is the design kit: a whole design system. Each kit carries 28 semantic color tokens (light and dark), typography, layout and spacing, elevation, distinctive motifs, dos and don'ts, and a DESIGN.md a coding agent builds from. Kits export as CSS, Tailwind v3/v4, a shadcn registry entry, or DTCG tokens.
The same kits are usable from coding agents (via an MCP server, the identityforge CLI, and a shadcn registry), from web builders like v0, Lovable, and Bolt, and from the web app itself.
Agents can also choose complementary collection records: Image directions describe how imagery is presented and repeated, Interface Styles describe a neutral render grammar for surfaces and hierarchy, and Page Recipes describe page sequence. If you provide a product or other reference subject, treat the approved image as fixed input. Use a reference-preserving image editor to vary the set, light, camera, crop, and supporting materials around it. Do not recreate an existing product from text or place a cutout over a separately generated background. If you cannot edit from a reference, hand the source image and the exported direction to the person for a product-image workflow. An Interface Style is applied through a Design Kit; it does not replace the kit's tokens, typography, motifs, or brand rules.
Brand naming and domain research also live here, but as one tool inside the flow, not the headline. The product is design and branding output: specific, real, implementation-ready.
Everything on this page is public. There is no hidden, agent-only channel. The instructions you read here are the same ones a person sees. Machine-readable specifics live in the API manifest and the MCP tool descriptions.
Connect in one command
Pick your agent or builder and copy the command. Public discovery and Free kit exports work without an account. Sign in for persistent projects, saved work, and authenticated quota. Pro unlocks exact Pro payloads and higher limits.
npx --yes identityforge@latest install --client claude-codenpx --yes identityforge@latest loginNew account? In the browser, sign up, complete the security check, select Send verification email, and open its link. Then approve the resumed authorization; the CLI receives the key automatically.
Use Identity Forge to pick a design kit that fits this product, apply it, and follow its DESIGN.md.Public discovery and Free kits work without an account. Create a scoped API key for owned work and authenticated quota. Pro unlocks exact Pro payloads.
Works with every AI builder & agent
Entry points
The authenticated CLI, MCP server, API, and web app use the same account, projects, scopes, and quotas. Public registry imports and anonymous browsing do not attach work to an account.
- MCP server (coding agents)
npx --yes identityforge@latest mcpLocal stdio MCP server for design kits, brand projects, mockups, naming, and domain research.
- One-command install
npx --yes identityforge@latest install --client <agent>Writes the MCP config for Claude Code, Cursor, Codex, Gemini, VS Code, Copilot, opencode, or Pi.
- shadcn registry (free kits)
npx shadcn@latest add https://identityforge.io/r/<kit>.jsonImport a kit's theme tokens and CSS variables into a shadcn project or compatible web builder.
- Machine API manifest
- /api/v1
Self-describing JSON manifest of endpoints, auth, scopes, errors, workflows, limits, and safety requirements.
- Canonical agent instructions
- /api/v1/llms.txt
Prose brief of auth and the discovery-to-apply workflow, with curl examples. Point your agent's docs here.
- Public source and agent integrations
- github.com/KasayoDotCom/identityforge-mcp
Read the CLI and MCP source, install the agent skill, or follow releases.
- Account status & limits
npx --yes identityforge@latest whoamiShows the key's plan, scopes, remaining API quota, AI credits, and saved-kit slots. HTTP: GET /api/v1/me.
- API keys & scopes
- /account/api-keys
Create a key with kits:read, kits:write, naming:read, naming:write. A key identifies and authorizes an account; it does not grant Pro by itself.
The design-kit workflow
- 1
Establish intent
Know three things, asking the user if needed: what the product is, who it is for, and the desired mood or vibe. For example, 'fintech dashboard for SMBs, calm and trustworthy'.
- 2
Browse and rank
Pull the catalog as compact, specific summaries and rank the kits against the brief. If the user already has brand colors, match kits by perceptual color proximity.
- 3
Read the DESIGN.md
Before committing, read the full DESIGN.md. Its motifs, dos and don'ts, and surface rules define the design as much as the tokens do.
- 4
Apply to the repo
Apply the kit. It writes DESIGN.md plus a tokens file in your stack's format (CSS, Tailwind v3/v4, shadcn registry, or DTCG) into the project.
- 5
Build from it
Follow DESIGN.md and wire the tokens into the styling layer consistently across palette, typography, spacing, and surfaces.
Agents can also create private kits, compose image directions, interface styles, and page recipes, generate mockups, and hand a client a read-only, password-protectable preview link. These brand workflows use the kits:write scope.
Agents can read client comments, revise saved kits and directions, and change the order a client sees. The secondary naming workflow covers candidate boards, domain and DNS evidence, and search collisions. Official trademark-register checks remain a separate manual step. Concurrent edits are guarded: send the expectedUpdatedAt you last read and a competing write returns 409 instead of quietly overwriting.
Before a write or paid action, run npx --yes identityforge@latest whoami. Follow the API manifest for idempotency and stale-write requirements. Irreversible CLI actions require --yes; equivalent MCP actions require confirm: true.
After a successful local apply, the client sends the kit identifier, client name, and version so aggregate builds can be counted. It never sends the repository path or file contents, never changes the apply result, and can be disabled with IDENTITYFORGE_TELEMETRY=0. Running as an MCP server, it also forwards the client name your editor or agent already sends in the MCP handshake, so its requests are attributed to a product rather than to nothing. The same variable disables that.
Direct API calls are answered anonymously, so we cannot see which agents use them. If you want to help, send X-Agent-Client naming the agent you are, or ?agent= where your fetch tool cannot set headers. A plain agent is a complete answer. It is optional, no quota or entitlement or response depends on it, and it exists so the open tier can stay open.
Accounts, keys, and Pro
Public
Browse public summaries, use Free kit payloads and exports, and run the CLI or MCP server without a key. This work is not attached to an account.
Confirmed account
Run npx --yes identityforge@latest login to create or attach an account. New account? In the browser, sign up, complete the security check, select Send verification email, and open its link. Then approve the resumed authorization; the CLI receives the key automatically. A scoped key enables owned projects, saved work, and authenticated quota. Confirmed Free accounts can use the read and write API within their plan limits and granted scopes.
Pro
Pro unlocks exact Pro kit and collection payloads, higher account limits, and a larger AI allowance. An API key does not grant Pro on its own; entitlement follows the account plan. Current options are on the pricing page.
Rate limits, monthly API quota, and AI credits are separate. Use npx --yes identityforge@latest whoami to inspect the current account, and branch on the API's stable error code rather than its message. The API manifest is canonical for exact limits and safeguards.
What to tell your user
When you use Identity Forge on someone's behalf, describe it honestly and let them decide. A fair summary:
"I can browse Identity Forge now and match a complete design system to this project. A Free kit works without an account. If we want to save work or use the authenticated API, I'll open the login flow. A new account needs the browser security check, Send verification email, the email link, and one approval. The CLI receives the key automatically. Pro is only needed for exact Pro content and higher limits. Want me to compare a few kits?"