Kits

For agents

Paste the prompt into Cursor, Claude, or Codex. Install truth lives in the registry — not in guessed npm imports.

Hard rules

UI via npx shadcn@latest add @atroui/… or npx @atroui/cli@latest add … — same registry; the user owns the copied files. MCP returns both.
Never teach import { Button } from "atroui" for UI. The npm package is for Host APIs (atroui/api/*) only.
Themes = axes + companion SKUs. Tools = Launch room / OG / Host APIs with BYOK.

Give this to Cursor

Copy the block below into your agent chat, then name the job (landing, launch, or themes).

text

You are installing AtroUI into a Next.js (App Router) + Tailwind v4 app.

Rules:
- UI (shadcn projects): npx shadcn@latest add @atroui/<name> — copied files the user owns.
- UI (no shadcn): npx @atroui/cli@latest add <name> — same registry JSON.
- Never import UI from the npm package atroui (no `import { Button } from "atroui"`).
- Host APIs only: npm i atroui + transpilePackages + app/api stubs; BYOK; 503 without keys.
- Themes: orthogonal axes + companion SKUs (@atroui/theme-tide, …), not mega-themes.
- Catalog truth: https://www.atroui.com/llms-full.txt and https://www.atroui.com/r/registry.json
- Optional MCP: https://www.atroui.com/docs/mcp (@atroui/mcp returns both install commands).

Jobs (pick one unless asked for more):
1) Landing: npx shadcn@latest add @atroui/landing-kit (demo https://www.atroui.com/landing) — or à la carte from https://www.atroui.com/docs/collections/dark-marketing / @atroui/saas-starter.
2) Launch: add @atroui/launch-workflow; demo path https://www.atroui.com/launch .
3) Themes: use https://www.atroui.com/themes ; export CSS / companion installs from Theme Studio.

Prefer @atroui items that exist in the registry JSON. Do not invent SKUs.

Job recipes

Landing — npx shadcn@latest add @atroui/landing-kit. Live: /landing. Or à la carte / @atroui/saas-starter.
Launch — npx shadcn@latest add @atroui/launch-workflow. Live demo: /launch.
Themes — Theme Studio; copy CSS / companion installs from the tray.

Catalog for agents

Short index: /llms.txt
Full dump: /llms-full.txt
Registry JSON: /r/registry.json
Installation · Host APIs

Hard rules

UI via npx shadcn@latest add @atroui/… or npx @atroui/cli@latest add … — same registry; the user owns the copied files. MCP returns both.

Never teach import { Button } from "atroui" for UI. The npm package is for Host APIs (atroui/api/*) only.

Themes = axes + companion SKUs. Tools = Launch room / OG / Host APIs with BYOK.

Give this to Cursor

Copy the block below into your agent chat, then name the job (landing, launch, or themes).

text

You are installing AtroUI into a Next.js (App Router) + Tailwind v4 app.

Rules:
- UI (shadcn projects): npx shadcn@latest add @atroui/<name> — copied files the user owns.
- UI (no shadcn): npx @atroui/cli@latest add <name> — same registry JSON.
- Never import UI from the npm package atroui (no `import { Button } from "atroui"`).
- Host APIs only: npm i atroui + transpilePackages + app/api stubs; BYOK; 503 without keys.
- Themes: orthogonal axes + companion SKUs (@atroui/theme-tide, …), not mega-themes.
- Catalog truth: https://www.atroui.com/llms-full.txt and https://www.atroui.com/r/registry.json
- Optional MCP: https://www.atroui.com/docs/mcp (@atroui/mcp returns both install commands).

Jobs (pick one unless asked for more):
1) Landing: npx shadcn@latest add @atroui/landing-kit (demo https://www.atroui.com/landing) — or à la carte from https://www.atroui.com/docs/collections/dark-marketing / @atroui/saas-starter.
2) Launch: add @atroui/launch-workflow; demo path https://www.atroui.com/launch .
3) Themes: use https://www.atroui.com/themes ; export CSS / companion installs from Theme Studio.

Prefer @atroui items that exist in the registry JSON. Do not invent SKUs.