Skip to content

Documentation

Build production interfaces with Cronus UI

Cronus UI is a product UI system. One command composes a themed SaaS from validated blocks. Catalog, registry, and Create studio are the pieces.

Project contract

The library is designed around semantic tokens, accessible primitives, and source-owned registry output.

Tokens

@cronus-ui/tokens owns semantic colors, radius, fonts, chart colors, CSS variables, and Tailwind v4 mappings.

Theme provider

@cronus-ui/theme applies presets and runtime overrides with CSS variables, so theme changes do not require component rewrites.

Component catalog

@cronus-ui/ui ships accessible primitives and composed patterns built with variants, focus states, and data-slot markers.

Registry

The CLI copies source-owned components into an app, resolves dependencies, and rewrites imports to local aliases.

Choose your path

Scaffold a SaaS with one command. Create Studio, Stack Builder, and the CLI remain for theme, stack, and existing apps.

For coding agents

Fetch the live catalog, or wire the MCP server. Both read the committed indices — not a hand-written list.

Current release

v0.7.6Released2026-09-09

official MCP Registry listing

io.github.pedrogbraz/cronus-ui is listed on the official MCP Registry: stdio via cronus-ui-mcp and Streamable HTTP at https://aicronus.com/mcp. npm latest is 0.7.6.

Release discipline

New components should land with docs, registry metadata, accessibility notes, and a changelog entry before they are considered ready for app adoption.