Decantr — Design Intelligence for AI-Generated UI

# Decantr > Design intelligence, governance, and verification for AI-generated UI. Decantr is the contract layer between product intent and AI-generated implementation — giving coding assistants structured design inputs, registry-backed UI knowledge, and scoped context files so they build coherent product surfaces instead of improvising screen by screen. Think of Decantr as **OpenAPI for AI-generated UI**: the model still writes the code, but Decantr defines the shape, vocabulary, and governance around it. Decantr separates design governance into two layers — **DNA** (durable visual axioms: theme, spacing, motion, accessibility, personality) and **Blueprint** (product topology: sections, page routes, shells, layouts, features). Strict where it should be strict, flexible where it should be flexible. ## Docs - [Homepage](https://decantr.ai/): What Decantr is and why AI-generated UI needs a contract layer. - [Workflow model](https://decantr.ai/reference/workflow-model.html): Brand new app, brownfield adoption, hybrid composition. - [Public API reference](https://decantr.ai/reference/registry-public-api.html): Registry endpoints, pack compilation, critique, audit. - [Package support matrix](https://decantr.ai/reference/package-support-matrix.html): Which packages are stable, beta, or experimental. ## Packages - [@decantr/cli](https://www.npmjs.com/package/@decantr/cli): Scaffold new apps, run checks, manage essence, search registry content. - [@decantr/mcp-server](https://www.npmjs.com/package/@decantr/mcp-server): MCP server exposing design intelligence to Claude, Cursor, Windsurf, VS Code, Zed, Continue.dev. Listed at `io.github.decantr-ai/mcp-server` in the official MCP Registry. - [@decantr/essence-spec](https://www.npmjs.com/package/@decantr/essence-spec): Essence schemas, validation, migration, TypeScript types. - [@decantr/registry](https://www.npmjs.com/package/@decantr/registry): Registry contracts, content utilities, API client surfaces. - [@decantr/