Getting started

Pick any path below. They all use the same design kits and exports.

CLI (recommended)

Browse the catalog, then apply one kit:

npx --yes identityforge@latest themes
npx --yes identityforge@latest apply ambient-sage --format css

apply writes DESIGN.md, the requested tokens, and an identityforge.json stamp. It refuses instead of overwriting untracked or locally edited files. Preview first with --preview.

Token formats: dtcg, css, tailwind-v3, tailwind-v4, and shadcn-registry.

For shadcn/ui projects, the registry install is the fastest path:

npx shadcn@latest add https://identityforge.io/r/ambient-sage.json

MCP server

Add the Identity Forge MCP server to your agent's configuration:

{
  "mcpServers": {
    "identityforge": {
      "command": "npx",
      "args": ["-y", "identityforge@latest", "mcp"]
    }
  }
}

Your agent can then browse kits, search by style or mood, and export tokens directly into the project.

API

Fetch any kit as JSON:

curl https://identityforge.io/api/v1/kits/ambient-sage

Export in a specific format:

curl 'https://identityforge.io/api/v1/kits/ambient-sage/export?format=css'

See the full API reference for all endpoints.

What happens next

Once a kit is in your project, your agent reads the rules in DESIGN.md and uses the token file for implementation. Commit the stamp so a later identityforge status can distinguish a changed kit, a changed document contract, and local file edits.

Read best practices for how to enforce token usage, pick component primitives, and generate variations.