K
@kana-consultant/ui-kit v0.2.0 · docs

Guides

AI agents

The kit ships with machine-readable reference files and a Claude Code Skill so AI coding assistants can use it correctly out of the box.

Discovery files

The docs site exposes three machine-readable entry points at the root:

  • /llms.txt — standard llms.txt index: a curated table of contents linking to every docs page, for agents that follow links.
  • /llms-full.txt — one-file full reference: install, setup, every primitive + block with short snippets, TanStack Form / Store patterns, rules for AI assistants. Drop this into a context window and you're done.
  • /skill.md — Claude Code Skill file with YAML frontmatter (name, description), ready to install.

Claude Code — install the skill

If you use Claude Code, you can drop the skill into your user-scope skills directory and Claude will load it automatically whenever it detects React admin / dashboard work:

Terminal 
mkdir -p ~/.claude/skills/kana-ui-kit
curl https://kana-ui-kit-docs.pages.dev/skill.md -o ~/.claude/skills/kana-ui-kit/SKILL.md

The skill's description frontmatter is scoped — Claude only loads it for React admin / internal-tool work. It stays out of the way for other projects.

Any other agent (Cursor, Windsurf, ChatGPT, Aider, etc.)

Point the agent at llms-full.txt. Either paste a prompt like: 

Read https://kana-ui-kit-docs.pages.dev/llms-full.txt, then
help me build an admin dashboard with @kana-consultant/ui-kit.

Or configure a project rule (Cursor example .cursorrules):

.cursorrules 
Use @kana-consultant/ui-kit for all UI. Reference:
https://kana-ui-kit-docs.pages.dev/llms-full.txt

Most modern agents will fetch the URL and ingest the reference. If your tool doesn't auto-fetch, download llms-full.txt and keep it in your repo — the file is stable and small (~8 KB).

What agents know from these files

  • How to install and wire Tailwind v4 (including the crucial @source line)
  • Every primitive and block with usage snippets
  • Naming conventions (T / I / E prefixes, kebab-case filenames)
  • TanStack Form / Store patterns, including the Zod-v4 per-field validator caveat
  • Skip rules (non-React, React Native, marketing pages)
  • Hard rules for generated code (import paths, enum usage, icon library)

MCP server

A Model Context Protocol server that exposes list_components / get_component / generate_usage tools is on the roadmap. For now, llms-full.txt + the Claude Skill cover most agent integrations.