Composed catalog

Default

Single-page starter

The smallest useful app: one page wired with the theme provider, anti-flash script, and a sample of metrics, a table, and cards to build from.

Aurora · dark

Scaffold

One command. Theme baked in as Aurora · dark.

bash

bunx create-cronus-app my-app

$ bunx create-cronus-app my-app

Catalog contract for this template. Defaults are this page's live entry.

Field	Type	Default	Description
`slug`*	`string`	`"default"`	Catalog id. Passed to create-cronus-app --template.
`command`*	`string`	`"bunx create-cronus-app my-app"`	Scaffold command for this template.
`kind`*	`"product" \| "landing" \| "starter"`	`"starter"`	Product app, marketing landing, or starter.
`path`*	`"gold" \| "compose" \| "showcase"`	`"compose"`	Gold path (saas/admin) vs composed catalog vs bundled showcase. Not a scaffold flag.
`theme`*	`"aurora" \| "neutral" \| "midnight" \| "sunset" \| "emerald"`	`"aurora"`	Default theme token pack.
`mode`*	`"dark" \| "light"`	`"dark"`	Default color mode.
`chrome`*	`{ navbar?: string; footer?: string }`	`{}`	Optional navbar and footer block slugs wrapping the stage.
`blocks`*	`TemplateBlockRef[]`	`[]`	Home-page stack of catalog blocks ({ block, variant? }).
`customStage`	`boolean`	—	Full custom stage instead of a stack of catalog blocks.
`inside`*	`string[]`	["One page: metric cards, orders table, invite card", "CronusUIProvider + anti-flash CronusThemeScript", "Tailwind v4 + token CSS pre-wired", "cronus-ui.json so `npx cronus-ui add` just works"]	What's included in the scaffold.

Navbar, page blocks, and footer in the order the composed home page stacks them.

Empty block stack.

$ bunx create-cronus-app my-app