Native Shell
Native Shell: AI-generated UI, native in your app, on every platform. Apps on iOS, Android, macOS, Windows and Linux, GPUI apps and web pages load signed, sandboxed TSX modules at run time and draw th
Base UI primitives behind a Kookie-owned API, generated OKLCH color, token-only styling.
Translation pending
Developer toolsTypeScript · CSSGitHub @KushagraDhawan1997OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
A design system that applies what research has measured, such as tap size and contrast, and decides everything else once, so every screen stays consistent.
Taken from the repository README
Loading the full README.
Read the full README ↗Kookie UI is a design system. A component library gives you parts and leaves the decisions to you. Kookie UI is the decisions: the rules, the patterns and the reason for each one. The components are how those decisions reach your screen.
Some design questions have measured answers. A fingertip needs a target of about 44 pixels, text needs enough contrast to read, and people group things that sit close together. Kookie UI applies these answers on every screen, and no prop can override them. Every other question is a judgment, such as a corner radius or the accent colour. Kookie UI makes each judgment once, in one place, so one change reaches every screen.
The same idea decides what a component is. Components are sorted by what they do, not by how they look, so tabs and a segmented control are two components, although both are a row of segments. Patterns, such as an app frame, a form or a dialog, are part of the system too, because consistency is won or lost where components meet.
The result is an app that stays consistent as it grows, because each decision is made in the system and not again in each file. Read the principles and the patterns at ui.kookie.design.
Pre-release. @kushagradhawan/kookie-ui-react is not on npm yet. Build the workspace to use it.
variant prop. tone states what a thing means. emphasis states how loud it
is. The two questions stay apart, so a quiet destructive action is expressible.gap on Flex, Stack and Grid.size is an index, not a measurement. One numeral joins a designed set: the height, the
inline padding, the corner, the icon box and the label step.depth is one word on the Theme. Each family then decides
what it does with light.Each of those is a refusal, and each refusal has a written reason and a stated escape.
The site in apps/docs is the documentation. It has four parts.
| route | what it holds |
|---|---|
/ | 26 guideline chapters: getting started, patterns and foundations |
/components | the reference for 64 components, with generated props tables and the refusals |
/builder | a composition editor that exports React code and reviews the result |
/preview and /matrix | the judging surfaces: real screens, and the axis grid |
any path + .md, or Accept: text/markdown | the same page as markdown, for an agent |
/llms.txt and /llms-full.txt | the index of every page, and the whole site in one file |
Run it:
pnpm install
pnpm run build
cd apps/docs && pnpm run dev
Build the package first. The documentation app imports the built output.
The library is built so that a coding agent learns it from the package rather than from you.
variant points at tone and emphasis, a margin prop points at Box..d.ts.@kushagradhawan/kookie-ui-react/eslint-plugin catches the three mistakes the compiler cannot see: a data-
axis attribute, utility classes or raw values in className and style, and a refused prop
inside a spread. It brings no parser, so a TypeScript project puts it after its own parser
entry.npx @kushagradhawan/kookie-ui-react init writes the library's rules into your AGENTS.md, CLAUDE.md or
.cursor/rules. It prints its plan first and changes nothing without --write.@kookie-ui/mcp is an MCP server with four tools, including check_usage, which reports
every refused prop, attribute, utility class and raw value in a piece of JSX..md, and /llms.txt lists them all.The AI agents chapter explains each one.
packages/ui @kushagradhawan/kookie-ui-react: the components, the token generator, the ESLint plugin and the tests
packages/mcp @kookie-ui/mcp: the MCP server, built from the documentation's own data
apps/docs the documentation site, the component reference and the builder
docs/ the governance documents
Run these from the repository root. They need pnpm 12 and Node 24.
| command | what it does |
|---|---|
pnpm run ci | build, test, lint and the CSS budget gate. Run this before you push. |
pnpm run build | checks the generated tokens, builds the JS and the types, bundles the stylesheet, then verifies the packed artifact |
pnpm run test | two projects: the generator laws in Node, the computed values in a browser |
pnpm run lint | ESLint and tsc --noEmit |
pnpm run measure | the CSS budget gate. The numbers live in packages/ui/budget.json. |
The token layer is generated. Regenerate it after you change packages/ui/src/tokens/config.ts:
pnpm --filter @kushagradhawan/kookie-ui-react run tokens
Read them in this order.
docs/THESIS.md states what the system is for and how it governs itself.docs/DECISIONS.md is the specification. It states what the system is now.docs/REVIEW.md holds the audits and what each one resolved.docs/ENGINEERING.md states the code conventions and the testing rules.docs/LOG.md is the dated decision log. It states how the system became this,
and what was rejected on the way.DECISIONS.md is what the system is. LOG.md is how it got there. The chapters in apps/docs
state both for a reader who did not make the decisions.
See CONTRIBUTING.md. The tests assert system laws, never snapshots, and a
law reads the value the browser computes rather than the value a stylesheet declares.
@shadcn/react package. Many part names, such as those of Dialog, Menu and Select, follow
shadcn/ui's.MIT.