@cronus-ui/ai-kit 0.6.0

package/templates/claude/skills/compose/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: compose
+description: Scaffold or grow a Cronus UI product (create-cronus-app templates, cronus-ui compose, add-page). Use when the user wants a new app, a new page, a SaaS/store/landing, or to assemble blocks into routes — not when they only want a single primitive.
+argument-hint: "[saas|store|landing|/route]"
+allowed-tools: Bash, Read, Edit, Write
+---
+
+# Scaffold or grow a Cronus UI product
+
+Cronus UI is a **product UI system**. Prefer assembling a validated app (templates →
+pages of installed blocks) over hand-rolling screens or calling `cronus-ui add` for
+every primitive. One control (button, dialog) is a different skill — defer to `ui-add`.
+
+Request: `$ARGUMENTS`
+
+## Product loop (preference order)
+
+1. **New app** — scaffold a template.
+2. **Grow** — add a page of installed blocks to an already-composed app.
+3. **Theme** — `theme` skill / `npx cronus-ui theme set` / MCP `set_theme` (Create Studio → `apply_theme`).
+4. **One piece** — `npx cronus-ui add <slug>` / MCP `install_component` (the `ui-add` skill).
+5. **Hand-roll** only if the registry has no matching component or block — then with semantic tokens.
+6. **Never** inline a Tailwind palette class (`bg-zinc-900`) or a raw hex.
+7. **Upgrade** — `npx cronus-ui upgrade --all --dry-run` first, then
+   `npx cronus-ui upgrade --all`. That pulls **component AND composed page/layout**
+   updates without losing local edits (3-way vs `.cronus-ui/base`).
+   Do NOT run `compose --overwrite` / `compose -o` to "upgrade" an existing app —
+   that wipes page edits. `--overwrite` is only for a fresh re-compose the user
+   asked to replace. MCP: `upgrade_components { "dryRun": true }` first, then
+   without dryRun. When the app was composed with `--manifest`, include
+   `"manifest": "path/to.json"`. Never `shadcn add` or overwrite blindly.
+
+If the cronus-ui MCP server is connected, prefer its write tools (`compose_app`,
+`add_page`, `set_theme`, `upgrade_components`) over shelling out. They spawn the same pinned CLI.
+
+## 1. New app
+
+Default marketing / product CTA is **`saas`**. If the user does **not** name a
+template, pass `--template saas`. **Never** run `create-cronus-app` without
+`--template`: the CLI default is `default` (an empty starter), which is the
+wrong CTA. `--yes` / `-y` without `--template` also falls through to `default`,
+so `-y` must go **together** with `--template saas`.
+
+Other composed templates: `store`, `landing`. Bundled (non-composed) starters:
+`default`, `dashboard`, `marketing` — only when the user explicitly asks for a
+minimal starter or those names.
+
+```sh
+npx create-cronus-app <name> --template saas
+npx create-cronus-app <name> --template saas -y
+npx create-cronus-app <name> --template store
+npx create-cronus-app <name> --template landing --theme sunset
+npx create-cronus-app <name> --template saas --no-install
+```
+
+Theme and mode belong on the **same** scaffold command (`DEFAULT_MODE` is already
+`dark`; pass `--mode dark` only to be explicit):
+
+```sh
+npx create-cronus-app <name> --template landing --theme sunset
+npx create-cronus-app <name> --template landing --theme sunset --mode dark
+```
+
+`--no-install` is a **create-cronus-app** flag (files only, skip `pm install`).
+`cronus-ui compose` / `add` / `add-page` use `--skip-install`, not `--no-install`.
+Do not mix them.
+
+This scaffolds the project **and** composes the template (pages + chrome from registry
+blocks). Do not recreate that tree by hand.
+
+## 2. Existing inited project (`cronus-ui.json` already there)
+
+```sh
+npx cronus-ui compose saas
+npx cronus-ui compose store --brand Acme -y
+npx cronus-ui compose landing --variant login=split --dry-run
+```
+
+Real flags (do not invent others):
+
+- `-y` / `--yes` — non-interactive (pick the first template if none is given).
+  **Always pass `-y` as an agent.** This is `cronus-ui compose`, not
+  `create-cronus-app` — on scaffold, `-y` still needs `--template saas`.
+- `-b, --brand <name>` — brand wordmark baked into chrome/hero.
+- `--variant <slug>=<id>` — repeatable, e.g. `--variant login=split`.
+- `--pages <list>` — comma-separated route subset, e.g. `--pages /,pricing`.
+- `--skip-install` — do not install npm dependencies. Not `--no-install`.
+- `--dry-run` — print the validated plan + per-file preview, write nothing.
+- `-o, --overwrite` — replace existing generated files. Only for a fresh
+  re-compose the user asked to replace — not how you pull template updates
+  (use `upgrade --all`).
+- `-r, --registry <source>` — registry URL or local directory.
+- `-m, --manifest <file>` — compose from an explicit manifest instead of a bundled template.
+
+MCP: `compose_app { "template": "saas", "brand": "Acme", "dryRun": false }`.
+
+## 3. Grow by one page
+
+```sh
+npx cronus-ui add-page --route /pricing --blocks pricing,cta --nav Pricing
+npx cronus-ui add-page --route /faq --blocks faq,cta --title FAQ --chrome site --dry-run
+npx cronus-ui add-page --route /login --blocks login=split --nav Login
+npx cronus-ui add-page --route /settings --blocks settings,account-security --nav Settings
+```
+
+The registry item is also `login--split`: `npx cronus-ui add login--split`.
+
+Real flags:
+
+- `--route <route>` — required, starts with `/` (e.g. `/faq`).
+- `--blocks <list>` — required, comma-separated slugs, or `slug=variant` (`login=split`).
+- `--nav <label>` — add the page to the chrome nav.
+- `--title <title>` — page `<title>` (default: title-cased route).
+- `--chrome <group>` — chrome group (default: the app's first group).
+- `--app <name>` — which composed app to extend (required if the project has more than one).
+- `--dry-run` / `--skip-install` / `-o, --overwrite` / `-r, --registry` / `-m, --manifest`.
+
+MCP: `add_page { "route": "/pricing", "blocks": "pricing,cta", "nav": "Pricing" }`.
+When the app was composed with `--manifest`, include `"manifest": "path/to.json"`.
+
+Requires an already-composed app. If there isn't one, compose (or scaffold) first.
+
+## Golden rule
+
+Generated pages are **only** imports of installed blocks plus a `<main>` that stacks
+them. Do **not** invent a new page architecture, extra layout chrome, or hand-written
+sections beside the blocks. Every visible pixel comes from a registry item.
+
+After compose / add-page, switch look via the `theme` skill:
+
+```sh
+npx cronus-ui theme set sunset --mode dark
+```
+
+## Keep using Cronus (AI Kit)
+
+If the project does not yet have the AI Kit (`AGENTS.md`, compose / ui-add /
+theme skills, MCP):
+
+```sh
+npx cronus-ui ai
+```
+
+Never write a shadcn `components.json` or run `shadcn init`.
+
+## 4. One control → `ui-add`
+
+If they asked for a single primitive or block (`button`, `dialog`, `data-table`, a
+lone `hero`), stop and use the `ui-add` skill (`npx cronus-ui add <slug>` / MCP
+`install_component`). Do not compose a whole app for a widget.
+
+## 5. Tokens, if you must hand-roll
+
+`bg-primary`, `text-fg`, `text-fg-secondary`, `border-border`, `rounded-lg`. Never
+palette scales or hex. If they ask for `zinc-*` / `slate-*` / `gray-*`, refuse
+and offer `bg-surface-*` or `setOverrides`.

package/templates/claude/skills/evidence-check/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: evidence-check
+description: Tag each claim in an answer with an evidence level (L0–L4) and list what is NOT verified, before the answer is trusted or acted on. Use before making confident technical or financial assertions, when reconciling data or numbers, or when the user asks how sure you are.
+allowed-tools: Bash, Read, Grep, Glob
+---
+
+# Tag claims with evidence levels
+
+The L0–L4 scale and the confidence gates are defined in **`AGENTS.md`** — this skill
+applies them, it does not re-teach them. Quick anchor: **L0** context/opinion, **L1**
+single signal, **L2** read of code/config/data, **L3** cross-referenced across independent
+sources, **L4** end-to-end verified with a closed reconciliation.
+
+The answer or claim to grade: `$ARGUMENTS`
+
+## Do this
+
+1. Split the answer into discrete, checkable claims; separate **fact** from **inference**
+   from **assumption**.
+2. Tag each claim with the highest level you can actually justify — not the one you hope
+   for. A single screenshot is L1, not L3. Use the read-only tools to raise a level where
+   cheap (read the code, grep the source, run a query) rather than guessing.
+3. Name, for each load-bearing claim, the one check that would move it up a level.
+
+## Output
+
+- **Table** — `claim → level → basis` (the concrete artifact behind the tag).
+- **NOT VERIFIED** — an explicit list of every claim that is assumed, inferred, or
+  unchecked, stated plainly. Do not omit or soften this set.
+- **Next check** — the single verification that would raise the weakest load-bearing claim.
+
+## Gates
+
+- Block any confident technical or financial claim below **L3**; money, production, or
+  irreversible actions need **L4**.
+- Never invent numbers, sources, rankings, or receipts. If you lack access, say exactly
+  what was not verified instead of filling the gap.
+- Do not label something "visual only", "harmless", or "already fine" before it has been
+  reconciled against the source.

package/templates/claude/skills/ship-pr/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: ship-pr
+description: Commit the working changes and open a pull request for __APP_NAME__. Use when the user asks to ship, commit, push, or open a PR — stage the change, write a small Conventional Commit with no AI attribution, push a dedicated branch, and open a PR whose body covers objective, changes, tests, risks, and rollback.
+argument-hint: ""
+allowed-tools: Bash, Read
+---
+
+# Commit and open a PR
+
+Turn the reviewed working changes into a clean, reviewable pull request.
+
+Optional PR title / scope: `$ARGUMENTS`
+
+## 1. Gate before shipping
+
+- Review the diff first if it hasn't been reviewed: run the `code-review` skill (inline, in
+  this session) or delegate to the `code-reviewer` subagent (fresh, isolated context).
+  Nothing P0/P1 ships below the 95% confidence gate (see `AGENTS.md`).
+- Confirm no debug instrumentation, secrets, or unrelated files are in the diff:
+  `git status` and `git diff`.
+
+## 2. Branch
+
+Never commit on the default branch. If you're on it, create a dedicated branch first:
+
+```sh
+git checkout -b <type>/<short-topic>   # feat/…, fix/…, chore/…, docs/…, refactor/…
+```
+
+## 3. Stage intentionally
+
+Add only the files that belong to this change — don't `git add -A` a dirty tree. Split
+unrelated work into separate commits or PRs.
+
+## 4. Commit
+
+Small commits in **Conventional Commits** form:
+
+```
+<type>(<scope>): <imperative summary>
+```
+
+`type` ∈ `feat | fix | refactor | docs | chore | test | perf`. Keep the subject short.
+**No AI attribution and no "generated by" trailers** anywhere in the message.
+
+## 5. Push and open the PR
+
+```sh
+git push -u origin HEAD
+gh pr create --title "<title>" --body "<body>"
+```
+
+The PR body must have these sections:
+
+- **Objective** — the problem and why this change.
+- **Changes** — what was done, key files/areas touched.
+- **Tests** — objective evidence: build/typecheck green, tests run, real flow exercised,
+  error path checked.
+- **Risks & attention points** — blast radius, shared contracts, anything a reviewer
+  should scrutinize.
+- **Rollback** — the named path back (e.g. revert this PR / this commit), safe to run.
+
+## 6. Deploy discipline
+
+Staging before production when applicable. Production or any environment mutation happens
+**only with explicit approval, a clear window, and the rollback named up front.**

package/templates/claude/skills/theme/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: theme
+description: Preview or switch the Cronus UI theme in __APP_NAME__. Use when the user wants to change the look, try a preset, toggle dark/light, or tweak brand color or radius — set the theme via the CLI, MCP, or useTheme, and never by inlining raw colors.
+argument-hint: "[preset]"
+allowed-tools: Read, Edit, Bash
+---
+
+# Preview or switch the app theme
+
+Cronus UI is themed entirely through CSS custom properties driven by the active preset,
+mode, and any token overrides. Changing them re-skins the whole app instantly — no
+per-component edits, no raw colors.
+
+Request: `$ARGUMENTS`
+
+## Presets and modes
+
+- Presets: **`aurora`** (default), **`neutral`**, **`midnight`**, **`sunset`**,
+  **`emerald`**.
+- Modes: **`light`**, **`dark`** (default `dark`).
+
+## Switch a baked-in preset (do this first)
+
+```sh
+npx cronus-ui theme set aurora
+npx cronus-ui theme set sunset --mode dark
+npx cronus-ui theme set neutral --mode light
+```
+
+`theme set` rewrites `defaultThemeName` / `defaultModeName` on the layout and records
+the choice in `cronus-ui.json`.
+
+MCP: `set_theme { "name": "sunset", "mode": "dark" }`. Use this for the five shipped
+presets. Before generating screens, call `get_design_context` (or read `DESIGN.md`)
+so the palette and look stay Cronus.
+
+## Apply a Create Studio theme
+
+```sh
+npx cronus-ui theme add <permalink|c=payload|file.json>
+npx cronus-ui theme add https://cronus-ui.dev/studio?c=... --dry-run
+```
+
+MCP: `apply_theme { "source": "<permalink|c=payload|file.json>", "dryRun": false }`.
+Prefer `apply_theme` for Studio permalinks; `set_theme` is only the baked-in presets.
+
+## Set the app default by editing the layout (only if the CLI is not an option)
+
+Edit `app/layout.tsx`. The `defaultThemeName` / `defaultModeName` on **`<CronusThemeScript>`**
+and **`<CronusUIProvider>`** must match, and both must use the same `storageKey`:
+
+```tsx
+<CronusThemeScript storageKey="theme" defaultThemeName="midnight" defaultModeName="dark" />
+...
+<CronusUIProvider asRoot storageKey="theme" defaultThemeName="midnight" defaultModeName="dark">
+```
+
+Also update the `theme` block in `cronus-ui.json` so newly added components scaffold with
+the same default. Keep `suppressHydrationWarning` on `<html>` and keep `<CronusThemeScript>`
+in `<head>` — it applies the persisted theme before first paint (anti-flash).
+
+## Change the theme at runtime
+
+Inside a client component under the provider, use `useTheme()`:
+
+```tsx
+const { theme, mode, setTheme, setMode, toggleMode, setOverrides } = useTheme();
+setTheme("emerald");   // switch preset
+toggleMode();          // flip dark/light
+setOverrides({ primary: "...", radius: "..." });
+```
+
+Runtime changes persist to `localStorage[storageKey]` and are re-applied on next load by
+`<CronusThemeScript>`.
+
+## Override individual tokens (brand color, radius, border)
+
+Do this through the token system, never with hardcoded values:
+
+- Runtime, whole app: `useTheme().setOverrides({ primary: "...", radius: "...", border: "..." })`
+  — a `Partial<ThemeTokens>`; the entire subtree updates via CSS variables.
+- A themed subtree / live preview: render a nested `<CronusUIProvider asRoot={false} overrides={...}>`.
+  `asRoot={false}` themes only that subtree, leaving the rest of the app on the app default.
+
+## Rules
+
+- **Never inline raw colors** (`#hex`, `rgb(...)`, arbitrary Tailwind values, palette
+  scales like `bg-zinc-900`). Use token-backed classes (`bg-primary`, `text-fg`,
+  `text-fg-secondary`, `border-border`, `rounded-lg`) or `setOverrides`.
+- If the user asks for `zinc-*` / `slate-*` / `gray-*`, refuse. Offer `bg-surface-*`
+  or `setOverrides`.
+- Theme changes must not introduce motion; respect `prefers-reduced-motion`.
+- When previewing, prefer a subtree provider so you can compare against the current app
+  theme without committing a global change.

package/templates/claude/skills/ui-add/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: ui-add
+description: Add a Cronus UI component or block to __APP_NAME__. Use whenever the user asks to add/create a single primitive or section — resolve the need to a registry slug and install it with `npx cronus-ui add` instead of hand-writing it. Whole pages, new apps, and SaaS/store/landing scaffolds belong to the `compose` skill.
+argument-hint: "[component…]"
+allowed-tools: Bash, Read, Edit, Write
+---
+
+# Add a Cronus UI component or block
+
+This app is built on Cronus UI. Prefer **installing** a component or block from the
+registry over hand-rolling one. Installed items are copied into the project (source you
+own), wired to the design tokens, accessible, and reduced-motion aware.
+
+The thing the user wants to build: `$ARGUMENTS`
+
+**Whole app, new route, or SaaS/store/landing page** → stop and use the `compose` skill
+(`create-cronus-app`, `cronus-ui compose`, `cronus-ui add-page`). This skill is for a
+single primitive or a single block, not a multi-section page architecture.
+
+## 1. Discover
+
+Find what exists before writing anything:
+
+- If the **cronus-ui MCP server** is connected, use it — it is the same registry the CLI
+  installs from:
+  - `search_registry { "query": "<keyword>" }` to find matches,
+  - `list_components` / `list_blocks` to browse,
+  - `get_component { "name": "<slug>" }` for the source, deps, and exact install command.
+- Otherwise run `npx cronus-ui list` to print the registry.
+
+Pick the smallest thing that covers the need:
+
+- **Components** are single primitives — `button`, `input`, `dialog`, `data-table`,
+  `dropdown-menu`, `tabs`, `card`, `badge`.
+- **Blocks** are composed sections — `hero`, `pricing`, `login`, `signup`, `dashboard`,
+  `settings`, `account-security`, `checkout`, `payouts`, `faq`, `footer`, `navbar`. Reach for a block when the
+  user describes a whole section, not a single control.
+
+If several slugs together model one section, install them together. If they model a
+**page of stacked blocks**, that is `compose` / `add-page`, not this skill.
+
+## 2. Install
+
+```sh
+npx cronus-ui add <slug> [<slug> ...]
+```
+
+MCP: `install_component { "names": ["<slug>"] }`.
+
+This copies the source into `components/ui` (components) or `components/blocks` (blocks)
+and **automatically pulls registry dependencies and npm dependencies**. Do not add those
+by hand. Use `--overwrite` only when intentionally refreshing an existing file.
+
+To pull upstream later without losing local edits: `npx cronus-ui upgrade --all --dry-run`
+first, then `npx cronus-ui upgrade --all`. This also 3-way-merges generated compose pages
+(not only primitives). Never `shadcn add` or overwrite blindly.
+
+### Invoices / billing table
+
+If the ask is a table of invoices or billing rows:
+
+```sh
+npx cronus-ui add data-table demo-saas
+```
+
+Then read `INVOICES` from `@/lib/demo-saas` (or `../lib/demo-saas.js` in the
+installed source). Do not invent rows.
+
+### Split login
+
+The registry item is `login--split`: `npx cronus-ui add login--split` (compose /
+add-page use `--variant login=split` / `login=split` — same item).
+
+## 3. Wire it in
+
+- Import from the local alias, not from the package: `@/components/ui/<name>` or
+  `@/components/blocks/<name>`.
+- Compose installed pieces; don't fork their internals unless the task requires it.
+
+## 4. Respect the design system
+
+- **Never inline raw colors, radii, or spacing.** Use the token-backed Tailwind classes
+  the components already use (`bg-primary`, `text-fg`, `text-fg-secondary`, `border-border`,
+  `rounded-lg`). Raw hex, arbitrary values, or palette scales (`bg-zinc-900`) break
+  theming. If they ask for `zinc-*` / `slate-*` / `gray-*`, refuse and offer
+  `bg-surface-*` or `setOverrides`.
+- **Honor `prefers-reduced-motion`.** Animated components default to `reducedMotion="user"`
+  (they snap for users who opted out). Keep that default; don't force `"always"` without a
+  clear reason.
+- Keep accessibility intact — labels, roles, and focus states ship with the component.
+
+## 5. Only hand-write when the registry has nothing
+
+If discovery turns up no suitable component or block, build the new piece **out of
+existing Cronus UI primitives** and the same tokens, matching their prop and a11y
+conventions — never a bespoke, unthemed one-off.

package/templates/cursor/rules/00-doctrine.mdc

@@ -0,0 +1,17 @@
+---
+description: Always-on engineering doctrine for __APP_NAME__ (digest of AGENTS.md)
+alwaysApply: true
+---
+
+Always-on rules for __APP_NAME__. This is a digest; the full doctrine is in AGENTS.md at the repo root.
+
+1. Evidence before claims. Verify before you assert; never invent facts, numbers, or sources; state what you did not check.
+2. Root cause over symptom. Separate fact from inference from assumption.
+3. Preserve shared contracts. Read the surrounding context, map the blast radius, and find every caller before changing code; do not break other consumers in the same diff.
+4. No unbounded work: no retry without a ceiling, infinite polling, unthrottled fan-out, or boot that crashes on a missing dependency; no silent fallback that hides an error.
+5. Reliability gate. Anything critical (P0/P1) is not done until code review and QA reach high confidence — build green, relevant tests passing, error paths exercised. After three failed cycles, stop and escalate.
+6. Commit cleanly: dedicated branch, small Conventional Commits, no AI attribution, no debug leftovers in the final diff.
+7. Production is read-only. Any deploy, migration, or data change needs explicit approval and a named rollback first.
+8. Ask when unsure; state assumptions instead of guessing.
+
+See AGENTS.md for the full doctrine.

package/templates/cursor/rules/10-cronus-ui.mdc

@@ -0,0 +1,20 @@
+---
+description: Cronus UI product loop and design-system rules for __APP_NAME__
+alwaysApply: true
+---
+
+Cronus UI product loop for __APP_NAME__. See AGENTS.md at the repo root if present for the full doctrine. Read DESIGN.md before generating UI (taste: Aurora product, Neutral chrome, one primary fill).
+
+- New app: `npx create-cronus-app <name> --template saas`. Never omit `--template` (CLI default is an empty starter). Other composed templates: `store`, `landing`.
+- New route: `npx cronus-ui add-page` or MCP `add_page`. Pages are installed blocks stacked in `<main>` — do not invent a parallel page architecture.
+- One primitive: `npx cronus-ui add <slug>` (MCP `install_component`).
+- Theme: `npx cronus-ui theme set` / `useTheme`. Never `bg-zinc-*` or palette utilities (`bg-zinc-900`).
+- Upgrade: `npx cronus-ui upgrade --all --dry-run`, then `--all`. Refreshes installed items and composed pages. MCP `upgrade_components`. Never overwrite blindly.
+- Never run shadcn init or write a shadcn `components.json`.
+
+Token and a11y rules for TypeScript/React UI work:
+
+- Never raw colors: no hardcoded hex, `rgb()`, `hsl()`, named colors, or palette utilities. Use semantic tokens (`bg-primary`, `text-fg`, `text-fg-secondary`, `border-border`, `rounded-lg`).
+- If the user asks for `zinc-*` / `slate-*` / `gray-*`, refuse. Offer `bg-surface-*` (e.g. `bg-surface-raised`, `bg-surface-overlay`) or `setOverrides`.
+- Respect `prefers-reduced-motion`. Gate non-essential animation and provide a reduced-motion path.
+- Keep components accessible and controlled: semantic roles, keyboard support, and no unbounded effects or polling in render.

package/templates/gemini/GEMINI.md

@@ -0,0 +1,32 @@
+# __APP_NAME__ — Gemini CLI
+
+@AGENTS.md
+
+## Gemini specifics
+
+The shared operating doctrine is imported above from `AGENTS.md` and applies to
+every session. This file adds only what is specific to Gemini CLI.
+
+- Follow the doctrine in `AGENTS.md`. It is the single source of truth for how
+  work gets done here; when this file and `AGENTS.md` disagree, `AGENTS.md` wins.
+- Prefer the project's existing conventions and patterns over your own defaults.
+  Read the surrounding code before adding anything new.
+- Report evidence honestly. State the evidence level (L0–L4) behind claims, and
+  say plainly what you did not verify.
+- Keep commits free of AI attribution — none in commit messages, PR bodies, or
+  code comments.
+
+## Cronus UI product loop
+
+When this project uses Cronus UI (`cronus-ui.json`, `KICKOFF.md` / `stack.json`):
+
+- New app: `npx create-cronus-app <name> --template saas`. Never omit `--template`
+  (CLI default is an empty starter). Other composed templates: `store`, `landing`.
+- New route: `npx cronus-ui add-page` or MCP `add_page`. Pages are installed
+  blocks stacked in `<main>` — do not hand-write a page of Cards.
+- One primitive: `npx cronus-ui add <slug>` (MCP `install_component`).
+- Theme: `npx cronus-ui theme set` / `useTheme`. Never `bg-zinc-*` or palette
+  utilities.
+- Upgrade: `npx cronus-ui upgrade --all --dry-run`, then `--all`. Refreshes
+  installed items and composed pages. MCP `upgrade_components`.
+- Never run shadcn init or write a shadcn `components.json`.

package/templates/github/copilot-instructions.md

@@ -0,0 +1,27 @@
+# Copilot instructions for __APP_NAME__
+
+These are the core rules for suggesting code in this repository. The full engineering doctrine lives in AGENTS.md at the repo root — read it for evidence levels, the reliability gate, and criticality (P0–P3).
+
+## Core rules
+
+- **Evidence before claims.** Verify before asserting. Never invent facts, numbers, APIs, files, or sources. Say what you did not check.
+- **Root cause over symptom.** Separate fact from inference from assumption. Attack the underlying cause, not the surface.
+- **Preserve shared contracts.** Before changing code, read the surrounding context, map the blast radius, and find every caller. Do not break other consumers in the same change; if you cannot fix them all in one diff, stop and report.
+- **No unbounded work.** No retry without a ceiling, no infinite polling or loops, no unthrottled fan-out, no boot that crashes on a missing dependency, and no silent fallback that hides an error.
+- **Meet the reliability gate.** Anything critical (P0/P1) is not done until code review and QA reach high confidence: build green, relevant tests passing, error paths exercised, correct target verified. After three failed correction cycles, stop and escalate.
+- **Commit cleanly.** Use a dedicated branch and small Conventional Commits. No AI attribution in commit messages or PRs. No debug instrumentation in the final diff. PRs state objective, changes, tests, risks, and rollback.
+- **Production is read-only.** Any deploy, migration, restart, or data change needs explicit approval and a named rollback first.
+- **Ask when unsure.** State assumptions instead of guessing.
+
+## UI work
+
+Follow the UI library selected in `KICKOFF.md` / `stack.json`. If Cronus UI is selected:
+
+- New app: `npx create-cronus-app <name> --template saas`. Never omit `--template` (CLI default is an empty starter). Other composed templates: `store`, `landing`.
+- New route: `npx cronus-ui add-page` or MCP `add_page`. Pages are installed blocks stacked in `<main>` — do not hand-write a page of Cards.
+- One primitive: `npx cronus-ui add <slug>` (MCP `install_component`).
+- Theme: `npx cronus-ui theme set` / `useTheme`. Never `bg-zinc-*` or palette utilities.
+- Upgrade: `npx cronus-ui upgrade --all --dry-run`, then `--all`. Refreshes installed items and composed pages. MCP `upgrade_components`.
+- Never run shadcn init or write a shadcn `components.json`.
+
+If another UI library or no UI library is selected, do not import Cronus UI packages unless the project explicitly adds them. Never inline raw colors and respect `prefers-reduced-motion`.

package/templates/mcp.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "cronus-ui": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "cronus-ui-mcp"]
+    }
+  }
+}

package/templates/windsurf/rules/doctrine.md

@@ -0,0 +1,25 @@
+---
+trigger: always_on
+---
+
+Always-on engineering doctrine for __APP_NAME__ (digest).
+
+- Evidence before claims. Verify before you assert; never invent facts, numbers, or sources, and say what you did not check.
+- Preserve shared contracts. Read the surrounding context, map the blast radius, and find every caller before changing code; don't break other consumers in the same diff.
+- No unbounded work. No retry without a ceiling, no infinite polling or effect loop, no unthrottled fan-out, no boot that crashes on a missing dependency, no silent fallback that hides an error.
+- Commit cleanly. Dedicated branch, small Conventional Commits, no AI attribution, no debug leftovers.
+- Ask when unsure. State assumptions instead of guessing.
+- Read before you write. Open the file and understand it before editing it.
+
+See AGENTS.md at the repo root for the full doctrine.
+
+## Cronus UI product loop
+
+When this project uses Cronus UI (`cronus-ui.json`, `KICKOFF.md` / `stack.json`):
+
+- New app: `npx create-cronus-app <name> --template saas`. Never omit `--template` (CLI default is an empty starter). Other composed templates: `store`, `landing`.
+- New route: `npx cronus-ui add-page` or MCP `add_page`. Pages are installed blocks stacked in `<main>` — do not hand-write a page of Cards.
+- One primitive: `npx cronus-ui add <slug>` (MCP `install_component`).
+- Theme: `npx cronus-ui theme set` / `useTheme`. Never `bg-zinc-*` or palette utilities.
+- Upgrade: `npx cronus-ui upgrade --all --dry-run`, then `--all`. Refreshes installed items and composed pages. MCP `upgrade_components`.
+- Never run shadcn init or write a shadcn `components.json`.