Introduction
Ark UI behaviour, design tokens, and one recipe every component follows.
Kanzo UI is the shared design system behind Kanzo's products. It is not a component grab-bag: every component is assembled the same way, so the whole surface re-themes from tokens and none of it drifts back into ad-hoc styling.
Installation
The packages, the peers you may not need, one stylesheet and one provider.
Philosophy
The rules the library is built on, and what earns a new component.
Styling
The recipe every component follows, and how you restyle one from outside.
Theming
Attributes on <html>, and why a wrapper cannot work.
Components
Every component in the library, grouped by use — generated from these docs.
Showcases
Whole screens, assembled the way a product does it.
What it is built on
Ark UI supplies behaviour — state, WAI-ARIA, keyboard, focus
management — and nothing about appearance. Shark UI supplies the
component recipes, adopted in the shadcn-style registry model and rebranded to our tokens — adopted,
not vendored: where we diverge, a measurement records why. The layout layer —
ShellRoot, SectionRoot and their parts — is ours, built to the same Ark idiom. Appearance is entirely design tokens
plus tailwind-variants recipes over Tailwind v4.
These docs are also a test
The library is consumed by React Server Component hosts, and a Vite playground structurally
cannot verify that: Vite ignores "use client" entirely. This site is a real App Router app
that prerenders every documented component on the server, so the boundary is exercised here
or nowhere. It runs in CI.