Introduction
KinetixUI is a cross-platform design system. One canonical DTCG token source is generated into each platform's native token output; the components on top of it are implemented by hand, natively, on each platform against a shared component contract. Nothing converts one platform's component code into another's. What keeps the implementations aligned is verification: CI checks every platform claim against real source, and the gaps are published. Which platforms exist, and how complete and how verified each one is, is on Supported platforms.
What you can install, and what you compile. React and Angular (preview) install from a package registry today. SwiftUI, Jetpack Compose and Flutter are real implementations, compiled in CI, not yet distributed as packages. Being undistributed is a fact about a package registry, not about the implementation — each native port is compiled by its own CI on every change.
- Tokens — DTCG token files, compiled by Style Dictionary into CSS variables, a TypeScript object, SwiftUI, Jetpack Compose, and Flutter. This is the only part that is generated.
- Components — a native implementation per platform of the same component contract: React (Radix primitives and Tailwind), Angular, SwiftUI, Jetpack Compose and Flutter, each idiomatic to its platform. React is one implementation, not the definition the others are copied from.
- Verification — a manifest declares which components exist on which platform, and CI fails when a claim has no source behind it.
- Registry — a component registry of our own, so you
npx @kinetixui/cli adda component and own the code outright. - This site — built entirely on
@kinetixui/uiand@kinetixui/tokens, in the same light and dark themes it documents.
On the web, nothing here has to be a runtime dependency you cannot patch. You copy
components into your app, along with the npm packages they import, and they become
yours. Copied code does not update itself: npx @kinetixui/cli add <name> --overwrite
replaces your copy, and any edits in it, with the current version.
Who it's for#
Product teams, agencies and companies shipping on more than one platform, who want one design language across all of them — with the differences between platforms documented rather than hidden. MIT licensed, all of it.
Evaluating rather than installing? Start with platform coverage for what exists where, then tokens for the architecture. The reference documentation below assumes you have decided.
How it flows#
Design tokens live as variables in the design source.
Six brand ramps, spacing, radius, and a Material-3 type scale are extracted
verbatim into tokens/primitives.
Semantic tokens map to the KinetixUI contract.
tokens/semantic/color.light.json aliases primitives to --primary,
--muted, --ring, and the rest. A generated color.dark.json mirrors it.
Style Dictionary compiles every platform.
pnpm build:tokens runs once per theme and writes
packages/tokens/dist/{web,ios,android,flutter}.
Each platform's components consume the contract.
The components are written separately per platform, and none of them hard-codes a
value: @kinetixui/ui uses bg-primary, text-muted-foreground, border-input, and
the native ports read the generated KinetixColors, spacing and radius. A token change
reaches every platform; a component change is made on each platform that has it.
Quickstart#
Initialise
npx @kinetixui/cli initWrites kinetixui.json and pulls the token contract into your globals.css.
It does not configure Tailwind: the components need Tailwind CSS 3 and the
preset from @kinetixui/ui, set up as in
Installation → Tailwind.
Add a component
npx @kinetixui/cli add buttonThe source lands in your repo under the path from kinetixui.json — no runtime
package.
Use it
import { Button } from "@/components/ui/button";
export default function Page() {
return <Button>Ship it</Button>;
}Next#
Full setup is on Installation; the contract and retheming live in Theming. Or jump straight to Button.