The component foundation built for generative UI. Your agent emits a JSON spec, a
guarded catalog validates it fail-closed, and real, accessible
ki-* components render it — in your brand, in any framework.
Drag a seam, click within a band, or use the arrow keys on a seam.Swipe the bands or pick a theme.
Every band is the same markup; only data-ki-theme and
data-ki-color-scheme change. Load your own theme as another token layer.
Theming guide
Theme
Scheme
Write it yourself, or let your agent compose it.
The same web components serve both. Hand-written UI imports them directly. Agent-written
UI goes through the catalog, which turns a spec into components only after it passes
validation.
By hand, in any framework
Standards-first custom elements: identical in plain HTML, React, Vue and Angular,
with generated, typed wrappers for the three frameworks.
Agents emit data, never code. Only catalog components render, only declared actions
dispatch, and protocol adapters translate A2UI and MCP Apps into the same path.
Render a specA2UIMCP server
import { renderUiSpec } from'@kimen/catalog';
const result = renderUiSpec(spec, {
surface: document.querySelector('#genui'),
onAction: (event) => agent.send(event.action),
});
if (!result.ok) console.warn(result.diagnostics);
# Build the server from the repository (pre-v1)
pnpm exec nx run @kimen/mcp-server:build
# Point Claude Code, or any MCP client, at it
claude mcp add kimen -- node --permission \
--allow-fs-read=/absolute/path/to/kimen/packages/mcp-server/dist/kimen-mcp.mjs \
/absolute/path/to/kimen/packages/mcp-server/dist/kimen-mcp.mjs
# Agents list the catalog, validate specs, render MCP Apps
The guardrail says no, and says why.
validateUiSpec
rejects a spec before anything renders, and names the offender and its path so a model
can repair it in one round. Select an example to see the recorded validator result.
Two runners are offline; queued jobs start within 4 minutes.
DraftLiveBetaFailed
OverviewRunsSettingsThree surfaces, one catalog, last validated two minutes ago.42 runs this week, none rejected.Allowed origins and declared actions.
onboarding.spec.jsonvalidated · 3 min agobilling.spec.jsonrejected · unknown-prop
Open a dialog
The draft and its two specs are removed for everyone in the workspace. This can't be
undone.
CancelDelete draft
Workspace
Settings shared with the team.
WorkspaceActivityRefreshReset
EmailInbox
DesignEngineering
Copy filename
New invitations will appear here.
Release date
Last update
Coverage
OpenReadyDraftReview
Kimen
ActionsPin workspaceDuplicateAbout retentionLogs are kept for 30 days.
The next sync starts at noon.Read the docs
RelayAtlasControl room
TodayWeek
AccountWorkspaceInvite
Services
Service
State
Relay
Ready
Atlas
Queued
Changes saved.Show a toast
A terracotta square crosses the frame.
Legible to agents, by contract.
Everything a model needs ships with the package and is generated from the source,
never written by hand. An API a capable agent can't wire correctly from its
description is treated as a defect.
The library as an index for language models, and all of it in one file.
@whenToUse@whenNotToUse
Usage guidance on every component, inside the contract itself.
@kimen/emitter
A system prompt, a provider-ready JSON Schema and a tool definition derived from
any catalog, plus a one-round repair loop.
kimen.dev/llms.txt
# @kimen/elements — Kimen web components> Kimen web components (ki-*). Standards-first Stencil
> components, tokens-only styling, agent-legible by contract.
Install with `pnpm add @kimen/elements @kimen/tokens`.
## Components
- [ki-button](https://kimen.dev/llms/ki-button.md): trigger the
single main action of a view, supporting actions in descending
hierarchy, or confirming/destructive actions through tone.
Protocol adaptersA2UI and MCP Apps available; AG-UI streams
reach the A2UI adapter
v1.0.0npm with trusted publishing and signed provenance
Capability status
Consumer catalog registration: your own components behind a JSON facade, validated and rendered through the same fail-closed guardrail
Emitter kit: model-agnostic prompt, catalog-specialized JSON Schema and tool definition so any LLM emits valid specs, with a single-round repair loop
Generated framework wrappers: @kimen/react, @kimen/vue and @kimen/angular with typed props, native events and each framework form idiom, drift-gated
Schema-constrained guarded renderer: untrusted UI specs render only through the neutral catalog, fail-closed
Kimen MCP server: over stdio, agents list and describe the catalog, validate UI specs with correctable issues and render them as MCP Apps surfaces through the guarded renderer
Changed-core mutation quality gate in hardening
A2UI protocol adapter: declarative A2UI messages render through the guarded renderer
MCP Apps adapter: Kimen surfaces reach MCP Apps hosts as self-contained ui:// resources rendered through the guarded renderer
Neutral runtime component catalog with schema-validated UI specs at the GenUI boundary
Machine-readable Web Components foundation with token-driven theming