Getting started

Pick any path below. All three give you the same kit, the same exports.

CLI (recommended)

npx identityforge@latest init

This walks you through picking a kit and writes the design tokens into your project. Or install a specific kit directly:

npx identityforge@latest kit install aurora-dawn --format css

Available formats: css, tailwind, design-md, json, style-dictionary, shadcn.

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

npx shadcn@latest add https://identityforge.io/api/v1/kits/aurora-dawn/shadcn-registry

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/aurora-dawn

Export in a specific format:

curl https://identityforge.io/api/v1/kits/aurora-dawn/export/css

See the full API reference for all endpoints.

What happens next

Once a kit is in your project, your agent uses the tokens from DESIGN.md (or the CSS/Tailwind config) to style every component. The kit is the single source of truth for the visual system. Change the kit, and every component repaints.

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