Working with AI

Registry

To use the Intent UI registry, add the following entry to your components.json:

{
  "registries": {
    "@intentui": "https://intentui.com/r/{name}"
  }
}

Initialize

Choose a client and run one of the following commands:

npx shadcn@latest mcp init --client codex

Add the following to ~/.codex/config.toml:

React Aria MCP

Use the React Aria MCP server to look up accessible primitives when building custom components beyond the Intent UI collection.

codex mcp add react-aria -- npx @react-aria/mcp@latest

Add the following to ~/.codex/config.toml:

If you use both MCP servers, your config should look like this:

Skills

Intent UI provides three independently installable Agent Skills in the main repository:

SkillUse it for
intentuiCreating, installing, reviewing, and debugging components; detects v3 and v4 from installed source
intentui-designv4-only purchased resources and the unified authenticated registry
intentui-migrateExplicit v3-to-v4 migration or a read-only upgrade audit

Install the skills from the Intent UI repository:

npx skills add irsyadadl/intentui

The CLI lets you select the skills and agents to install. Use --skill intentui to choose only the component skill, and npx skills update to update installed skills.

The component skill resolves your application's aliases and framework paths, reads actual component APIs, and loads only relevant rules. It preserves local customizations and never upgrades ordinary component work implicitly. Version-specific overlays and semantic colors live inside the same skill.

Design Intent UI registry

Design Intent UI targets v4 and includes the public components and premium resources in one authenticated registry. Licensed v4 users need only @irsyad, including when installing Button, Dialog, or Table:

{
  "registries": {
    "@irsyad": {
      "url": "https://design.intentui.com/r/{name}",
      "headers": { "Authorization": "Bearer ${REGISTRY_TOKEN}" }
    }
  }
}

Public-only users can keep the @intentui setup above. Both registries may coexist, but v4 Design workflows prefer @irsyad; adding a duplicate public entry is unnecessary. Existing configuration and headers are preserved. Keep tokens private and follow the Design setup. A configured token does not prove access, and not every kit or template is a registry item.

Design resources require v4. For an older project, request an audit or migration with intentui-migrate; ordinary component work never upgrades automatically. The migration skill includes dry-run codemods for semantic tokens and simple Modal consumers, while complex overlay changes remain source-aware migrations.

The existing shadcn MCP server supplies registry discovery, search, item inspection, examples, and installation commands. Skills supply conventions and workflows. When MCP is unavailable, the skills use the project's shadcn CLI runner. No separate Intent UI MCP server is required.

See the skill guide for installation, authentication, compatibility, migration, and contribution instructions.

Markdown files

Every page in the docs is also published as a standalone Markdown file.

To view it, add .md to the end of the page URL. You can also use the Copy page button on each page to copy the full content to your clipboard as Markdown.

llms.txt

The llms.txt file provides an index of Intent UI documentation pages.

References

Design
Tracker
Laravel