Docs
How kitr works, from your first app to writing your own packages. Pick what you are trying to do, or browse every page below.
If you want to…
Start here
What is kitrThe mental model for kitr in five minutes: platforms, packages, kits and providers, and what it is built on.Getting startedInstall kitr, create your first app and add a package, in about five minutes.Project structureWhere every kind of file in a kitr app lives, what it is called, and the command that writes it.ConfigurationHow kitrrc.ts, config files, providers and environment variables fit together.
Concepts
Loading and saving dataThe one idea that ties kitr together, a single contract for every data source.Built for agentsWhy kitr suits coding agents, how to install the Claude Code plugin, and what an agent gets from the CLI.How kitr comparesWhere kitr overlaps with Next.js, Remix and React Router, TanStack Start, Expo, AdonisJS and Laravel, and when to pick each.
Extend
Add your own codeAdd your own state, services and drivers in three steps: a provider in your project, a swapped driver, a package of your own.Building a packageWrite a kitr package that the CLI can install and this site can list, with docs and a live example.Package contractHow a package plugs into kitr add, the CLI and the build: questions, codemods, commands, generators.
Reference
CLIEvery kitr command and flag.KitsWhat each kit sets up, what the presets scaffold, and how to write a kit of your own.PlatformsWeb, server, desktop and mobile platforms: options, commands and layout.Choosing a data sourceActions, API routes, HTTP or realtime: which one to use, what each kit chose and how they mix.PackagesWhat each package provides, which kit includes it, and the roadmap.Entry pointsHow @kitr/* packages wrap upstream libraries, and the rules behind them.Design decisionsThe rules behind kitr's architecture and what each one means for your code.GlossaryThe words kitr uses, each in one line: platform, package, kit, provider, contract, effects and more.