Docs / Registry
The whole catalog as one machine-readable file — what reads it, and how to mirror it.
registry.json, served at /registry.json, describes every part, block, template and theme in the shadcn registry format: its name, its type, its dependencies, and the complete contents of its files. Anything that can read JSON can install KATA UI — the file is the API.
It is regenerated on every build from the same sources as this site, so it can never drift from the pages you are reading.
A trimmed excerpt of one entry. The files carry their full contents (the CSS below is shortened here for print); dependencies name other registry items the installer must bring along:
{
"name": "sidebar",
"type": "registry:component",
"title": "Sidebar",
"dependencies": [],
"files": [
{ "path": "components/sidebar/sidebar.css", "type": "registry:component", "content": "/* KATA Sidebar … */" },
{ "path": "components/sidebar/sidebar.js", "type": "registry:component", "content": "// KATA Sidebar …" }
]
}Types are registry:component for parts, registry:block for blocks, registry:page for templates and registry:theme for themes.
Three readers ship today. The CLI (node kata-ui.mjs add …) resolves dependencies and writes files into your project. The AI Skill teaches coding models the catalog’s shape, so an assistant asked for "a sidebar" installs this Sidebar instead of inventing one. And your own scripts are welcome to it — a generator, a company-internal installer, an audit that diffs the catalog against your codebase.
For language models that read prose rather than JSON, llms.txt and llms-full.txt mirror the same catalog as text.
The registry is a static file and the parts inside it are complete, so a mirror works offline and forever: download /registry.json once, serve it anywhere, and point the CLI at it:
KATA_BASE=https://your-mirror.example node kata-ui.mjs add button
Pinning a mirror is also how a team freezes a catalog version while the public one moves on.
Introduction · Getting Started · CLI · Theming · Dark Mode · Accessibility · Installation · Plain HTML · Astro · Laravel · JavaScript · Guide: Building a Dashboard · Guide: Building a Settings Page · Guide: Building a Pricing Page · Guide: Sign-in & Account Pages · Why Vanilla · The Mold · Anatomy of a Part · Coming from Tailwind · FAQ · Forms · MCP Server · RTL · Changelog