API Reference
Tabula ships as ten @tabula-css/* packages that form one pipeline. You author flat DTCG design tokens, tabula build (the cli) turns them into generated .tabula/ artifacts and a registry.json (via tokens and registry), and that registry is then read at runtime by the merge functions (merge) and the Tailwind entry stylesheet (preset), enforced in your editor and CI by the linters (eslint-plugin, stylelint-plugin), and exposed to coding agents through the mcp server and the generated llms.txt. core is the zero-dependency contract every other package imports its invariants from, and react is an optional set of paved-path components built on top of merge.
Foundation
@tabula-css/core— Tabula contract-as-code: frozen tables, pure functions, error codes, and JSON Schemas. Zero runtime dependencies.@tabula-css/tokens— Tabula flat-DTCG-profile parser, value-semantics validator, axis resolver, and emitters.@tabula-css/registry— Tabula registry generator (two-backend oracle) and the Tailwind-free registry reader consumed by merge/eslint/mcp.
Runtime
@tabula-css/merge— Tabula runtime merge:cn(),resolve(),dyn(). Reads the registry only (no Tailwind dependency); the mathematical heart of the profile.@tabula-css/preset— Tabula Tailwind v4 entry assembly:@import "tailwindcss" source(none)+@theme+@source inline()over the whole vocabulary. Pure library — the CLI writes the files.@tabula-css/react— Optional Tabula paved-path primitives:<Text>,<Separator>,<Prose>. Registry-backed merge; no Tailwind in the import graph.
Tooling
@tabula-css/cli— ThetabulaCLI:build,build --check,check:css,scan,migrate,except add,doctor,explain,canary.@tabula-css/eslint-plugin— Tabula enforcement layer: the flat-config ESLint plugin that makes the closed vocabulary a hard gate. Reads the registry only (SPEC J15 — no Tailwind in its import graph).@tabula-css/stylelint-plugin— Tabula CSS governance: the five project-CSS rules (no@apply, no hand-authored rules, root-only custom properties, no@theme inline, no!important) as stylelint rules, plus the PostCSS kerneltabula check:cssruns.
Agent surface
@tabula-css/mcp— Tabula's read-only MCP server: the agent-facing surface over the generated.tabula/artifacts.
See also
- Getting started — a from-zero walkthrough across this whole pipeline.
- Concepts — locality, the registry, the merge algorithm, profile levels, theming, and the banned-mechanism catalog.
- Agent surface —
llms.txt, the MCP tools, and the fail-visible guarantees the agent surface relies on.