create-patties 0.0.11 → 0.0.12

package/src/prompts.ts

@@ -1,12 +1,15 @@
-// Interactive prompts for create-patties. See spec cli/09-create-patties-dx
-// items 3 + 5. Uses Bun's built-in prompt() — no new dependency.
+// Interactive prompts for create-patties. See cli specs 09 + 18.
+// Uses Bun's built-in prompt() — no new dependency.
 //
 // Non-TTY callers must supply the equivalent flags; the run loop only invokes
-// these helpers when stdin is a TTY and --yes was not passed.
+// these helpers when stdin is a TTY and --yes was not passed. The prompt order
+// (spec 18) is gated by project type: UI is asked only for frontend/fullstack,
+// monorepo only for fullstack, and the deploy target option set depends on type.
 
 export type AgentTemplate = "claude" | "codex" | "none";
-export type Target = "bun" | "edge";
-export type Scaffold = "demo" | "blank";
+export type ProjectType = "frontend" | "backend" | "fullstack";
+export type Target = "bun" | "edge" | "container";
+export type Theme = "neutral" | "slate" | "stone" | "zinc";
 export type Deploy =
 	| "cloudflare"
 	| "vercel"
@@ -48,41 +51,83 @@ export function promptName(
 	return undefined;
 }
 
+// "old school" is the TTY label for the no-agent choice; the flag value stays
+// `none` (spec 18). `--template` remains an alias for `--agent`.
 export function promptAgent(io: PromptIO = {}): AgentTemplate {
 	const ask = io.prompt ?? prompt;
 	const answer = (
-		ask("Which AI coding agent will you use? [claude/codex/none] (claude) ") ??
-		""
+		ask(
+			"Which coding agent are you using? [Claude/Codex/old school] (Claude) ",
+		) ?? ""
 	)
 		.trim()
 		.toLowerCase();
 	if (answer === "codex") return "codex";
-	if (answer === "none") return "none";
+	if (answer === "none" || answer === "old school" || answer === "old-school") {
+		return "none";
+	}
 	return "claude";
 }
 
-export function promptScaffold(io: PromptIO = {}): Scaffold {
+export function promptType(io: PromptIO = {}): ProjectType {
 	const ask = io.prompt ?? prompt;
-	const answer = (ask("Include the interactive todo demo? [Y/n] (Y) ") ?? "")
+	const answer = (
+		ask(
+			"What kind of project are you building? [frontend/backend/fullstack] (fullstack) ",
+		) ?? ""
+	)
 		.trim()
 		.toLowerCase();
-	if (answer === "n" || answer === "no" || answer === "blank") return "blank";
-	return "demo";
+	if (answer === "frontend") return "frontend";
+	if (answer === "backend") return "backend";
+	return "fullstack";
 }
 
-export function promptTarget(io: PromptIO = {}): Target {
+// Asked only for frontend/fullstack — backend has no UI surface.
+export function promptUi(io: PromptIO = {}): boolean {
 	const ask = io.prompt ?? prompt;
-	const answer = (ask("Runtime target? [bun/edge] (bun) ") ?? "")
+	const answer = (
+		ask("Do you want a styled UI template (Patties UI)? [Y/n] (Y) ") ?? ""
+	)
 		.trim()
 		.toLowerCase();
-	return answer === "edge" ? "edge" : "bun";
+	return !(answer === "n" || answer === "no");
+}
+
+// Asked only for fullstack.
+export function promptMonorepo(io: PromptIO = {}): boolean {
+	const ask = io.prompt ?? prompt;
+	const answer = (ask("Do you want a monorepo structure? [y/N] (N) ") ?? "")
+		.trim()
+		.toLowerCase();
+	return answer === "y" || answer === "yes";
+}
+
+// The option set depends on project type: container is fullstack-only.
+export function promptTarget(type: ProjectType, io: PromptIO = {}): Target {
+	const ask = io.prompt ?? prompt;
+	const options = type === "fullstack" ? "bun/edge/container" : "bun/edge";
+	const answer = (ask(`Where will you deploy? [${options}] (bun) `) ?? "")
+		.trim()
+		.toLowerCase();
+	if (answer === "edge" || answer === "worker" || answer === "worker/edge") {
+		return "edge";
+	}
+	if (
+		type === "fullstack" &&
+		(answer === "container" ||
+			answer === "docker" ||
+			answer === "container/docker")
+	) {
+		return "container";
+	}
+	return "bun";
 }
 
 export function promptDeploy(io: PromptIO = {}): Deploy {
 	const ask = io.prompt ?? prompt;
 	const answer = (
-		ask("Deploy plugin? [cloudflare/vercel/deno/netlify/bun/none] (none) ") ??
-		""
+		ask("Deploy plugin? [cloudflare/vercel/deno/netlify/none] (none) ") ?? ""
 	)
 		.trim()
 		.toLowerCase();

package/src/readme.ts

@@ -4,8 +4,9 @@
 //   1. Strip/keep conditional blocks delimited by:
 //        <!-- if:KEY=VALUE -->...<!-- /if -->
 //      The block is kept iff `vars[KEY] === VALUE`.
-//   2. Replace `{{name}}`, `{{agent}}`, `{{target}}`, `{{deploy}}` placeholders
-//      with the corresponding `vars` entry.
+//   2. Replace `{{name}}`, `{{agent}}`, `{{type}}`, `{{ui}}`, `{{monorepo}}`,
+//      `{{app_name}}`, `{{target}}`, `{{deploy}}` placeholders with the
+//      corresponding `vars` entry.
 //
 // `renderTemplatesInTree` walks a scaffolded project and applies the template
 // to every text file we care about (README.md, *.md, *.json, *.ts, *.tsx).
@@ -14,9 +15,12 @@
 export interface TemplateVars {
 	name: string;
 	agent: "claude" | "codex" | "none";
-	target: "bun" | "edge";
+	type: "frontend" | "backend" | "fullstack";
+	ui: "yes" | "no";
+	monorepo: "yes" | "no";
+	target: "bun" | "edge" | "container";
 	deploy: "cloudflare" | "vercel" | "deno" | "netlify" | "bun" | "none";
-	scaffold: "demo" | "blank";
+	app_name: string;
 }
 
 const CONDITIONAL_RE =
@@ -37,9 +41,12 @@ export function applyTemplate(source: string, vars: TemplateVars): string {
 		stripped
 			.replaceAll("{{name}}", vars.name)
 			.replaceAll("{{agent}}", vars.agent)
+			.replaceAll("{{type}}", vars.type)
+			.replaceAll("{{ui}}", vars.ui)
+			.replaceAll("{{monorepo}}", vars.monorepo)
+			.replaceAll("{{app_name}}", vars.app_name)
 			.replaceAll("{{target}}", vars.target)
 			.replaceAll("{{deploy}}", vars.deploy)
-			.replaceAll("{{scaffold}}", vars.scaffold)
 			// Legacy placeholders from earlier overlay revisions — kept so existing
 			// CLAUDE.md / AGENTS.md template text keeps interpolating.
 			.replaceAll("{{PROJECT_NAME}}", vars.name)

package/src/ui.ts

@@ -0,0 +1,93 @@
+// Patties UI starter integration (spec 18 §Patties UI).
+//
+// create-patties stays zero-dependency and offline, so instead of shelling out
+// to `patties ui init` + `patties add` (which need the project's installed
+// binary) we vendor the starter set under templates/ui-starter/ and copy it
+// directly. The vendored copies are byte-for-byte identical to
+// packages/patties-ui/templates/ — a drift test enforces that — so this is
+// equivalent to what `patties add button card input label` would stamp.
+
+import { existsSync } from "node:fs";
+import { resolve } from "node:path";
+import type { Theme } from "./prompts.ts";
+
+// Runtime peer deps the starter components + _internal helpers import.
+// Derived from packages/patties-ui/src/registry.ts entries for the starter set:
+//   button → cn + cva, card → cn, input → cn, label → cn + @radix-ui/react-label
+export const UI_DEPS: Record<string, string> = {
+	"@radix-ui/react-label": "^2.1.0",
+	"class-variance-authority": "^0.7.0",
+	clsx: "^2.1.0",
+	"tailwind-merge": "^2.5.0",
+};
+
+// Dev-only: the catalog the user runs `patties add` / `patties ui` against.
+export const UI_DEV_DEPS: Record<string, string> = {
+	"patties-ui": "latest",
+};
+
+const STARTER_COMPONENTS = ["button", "card", "input", "label"] as const;
+
+// Stamp the vendored starter set into an app directory and rewrite the demo to
+// import the stamped components. `uiStarterDir` is templates/ui-starter.
+export async function applyUiStarter(
+	appRoot: string,
+	theme: Theme,
+	uiStarterDir: string,
+): Promise<void> {
+	const uiDir = `${appRoot}/app/components/ui`;
+	const internalDir = `${uiDir}/_internal`;
+	const stylesDir = `${appRoot}/app/styles`;
+	await Bun.$`mkdir -p ${internalDir} ${stylesDir}`.quiet();
+
+	for (const name of STARTER_COMPONENTS) {
+		await Bun.$`cp ${uiStarterDir}/${name}.tsx ${uiDir}/${name}.tsx`.quiet();
+	}
+	await Bun.$`cp -R ${uiStarterDir}/_internal/. ${internalDir}`.quiet();
+
+	const themeTokens = resolve(uiStarterDir, "themes", theme, "tokens.css");
+	const tokens = existsSync(themeTokens)
+		? themeTokens
+		: resolve(uiStarterDir, "tokens.css");
+	await Bun.$`cp ${tokens} ${stylesDir}/tokens.css`.quiet();
+	// app.css is written (not vendored) because a committed `@theme` stylesheet
+	// would trip this repo's Biome CSS parser, which has Tailwind directives off.
+	await Bun.write(`${stylesDir}/app.css`, APP_CSS);
+
+	// Demo page + island that import the stamped components. Only applies to
+	// frontend / fullstack, which always have app/routes + app/islands.
+	await Bun.$`cp ${uiStarterDir}/demo/index.tsx ${appRoot}/app/routes/index.tsx`.quiet();
+	await Bun.$`cp ${uiStarterDir}/demo/TodoApp.tsx ${appRoot}/app/islands/TodoApp.tsx`.quiet();
+}
+
+// Pre-wired Tailwind v4 + tokens stylesheet (the wiring `patties ui init`
+// prints). Patties does not bundle Tailwind — compile this with the Tailwind
+// CLI; see the generated README "Styling" section.
+const APP_CSS = `@import "tailwindcss";
+@import "./tokens.css";
+
+@theme inline {
+	--color-background: var(--background);
+	--color-foreground: var(--foreground);
+	--color-card: var(--card);
+	--color-card-foreground: var(--card-foreground);
+	--color-popover: var(--popover);
+	--color-popover-foreground: var(--popover-foreground);
+	--color-primary: var(--primary);
+	--color-primary-foreground: var(--primary-foreground);
+	--color-secondary: var(--secondary);
+	--color-secondary-foreground: var(--secondary-foreground);
+	--color-muted: var(--muted);
+	--color-muted-foreground: var(--muted-foreground);
+	--color-accent: var(--accent);
+	--color-accent-foreground: var(--accent-foreground);
+	--color-destructive: var(--destructive);
+	--color-destructive-foreground: var(--destructive-foreground);
+	--color-border: var(--border);
+	--color-input: var(--input);
+	--color-ring: var(--ring);
+	--radius-lg: var(--radius);
+	--radius-md: calc(var(--radius) - 2px);
+	--radius-sm: calc(var(--radius) - 4px);
+}
+`;

package/templates/_backend/app/routes/api/todos.ts

@@ -0,0 +1,30 @@
+import type { PattiesContext } from "patties/middleware";
+
+// A small in-memory sample resource so a backend project boots with a working
+// endpoint. Swap the array for a real data source when you're ready.
+interface Todo {
+	id: number;
+	text: string;
+	done: boolean;
+}
+
+const todos: Todo[] = [
+	{ id: 1, text: "wire up a database", done: false },
+	{ id: 2, text: "add authentication", done: false },
+];
+
+export function GET(_req: Request, ctx: PattiesContext): Response {
+	return ctx.json({ todos });
+}
+
+export async function POST(
+	req: Request,
+	ctx: PattiesContext,
+): Promise<Response> {
+	const body = (await req.json()) as { text?: unknown };
+	const text = typeof body.text === "string" ? body.text.trim() : "";
+	if (!text) return ctx.json({ error: "text is required" }, { status: 400 });
+	const todo: Todo = { id: todos.length + 1, text, done: false };
+	todos.push(todo);
+	return ctx.json({ todo }, { status: 201 });
+}

package/templates/_claude/.claude/commands/patties-init.md

@@ -0,0 +1,33 @@
+---
+description: Guided, plan-mode first scaffold for a Patties project — pick feature patterns, see a plan, then scaffold after approval.
+---
+
+# /patties-init
+
+Guide the user through their first feature scaffold. This command is a thin
+driver — all the recipe detail lives in the `patties` skill. Do **not**
+duplicate the pattern catalog here; defer to `/patties`.
+
+You are (or should be) in **plan mode**: explore and propose, but write nothing
+until the user approves the plan.
+
+Run these four steps:
+
+1. **Discover** — read the project to fit the plan to what was scaffolded:
+   - project type (frontend / backend / fullstack) and deploy target, from
+     `patties.config.ts` and `package.json`,
+   - whether Patties UI is initialized (does `app/components/ui/_internal/`
+     exist?),
+   - flat vs. monorepo layout (is there an `apps/` workspace?).
+2. **Ask** — which feature pattern(s) from the `patties` skill catalog the user
+   wants (auth-rbac, crm, task, pivot, dashboard), plus the domain specifics the
+   recipes adapt to: entity names, fields, and roles.
+3. **Plan** — present the file list, the `patties add` components to stamp, and
+   the mock-data shape, honoring the skill's **UI + mock data** depth contract
+   (no `bun:sqlite`, migrations, or real backend). Write nothing yet.
+4. **Scaffold** — once the user approves and exits plan mode, generate the files
+   per the `patties` skill recipes. If the catalog isn't initialized, run
+   `patties ui init` first.
+
+For ongoing work after this first scaffold (adding one component or one more
+pattern later), the user invokes the `/patties` skill directly.

package/templates/_claude/.claude/skills/patties/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: patties
+description: Use when adding a Patties UI component or scaffolding a feature pattern (auth + RBAC, CRM, task board, pivot table, dashboard). Trigger phrases include "add a component", "scaffold a CRM / dashboard / auth", "patties pattern", "/patties".
+---
+
+# /patties — components & feature patterns
+
+## When to use
+
+Use this when the user wants to **add a Patties UI component** or **scaffold a
+feature pattern** (auth + RBAC, a CRM, a task board, a pivot table, a
+dashboard). It covers scaffolding only — for running, building, deploying, or
+managing secrets, use the `patties-cli` skill instead.
+
+Two capabilities:
+
+1. **Add a UI component** — a thin wrapper over the deterministic catalog.
+2. **Scaffold a feature pattern** — instruction-driven: you generate the files,
+   adapting names/fields/copy to the user's domain.
+
+## Add a component
+
+The component catalog is deterministic — never hand-author component source; the
+registry is the source of truth.
+
+1. If `app/components/ui/_internal/` does not exist, the catalog isn't
+   initialized — run `patties ui init` first (pass `--theme <neutral|slate|stone|zinc>`
+   to match the project).
+2. Run `patties add <name>` (preview first with `patties view <name>` or
+   `patties add --view <name>` if the user wants to see the source).
+3. Import the stamped component from `app/components/ui/<name>.tsx` and use it.
+
+`patties add` edits `package.json` (it never runs an install) and stamps source
+into `app/components/ui/`. After adding, remind the user to run `bun install` if
+new peer deps were added.
+
+## Scaffold a pattern
+
+Pick the pattern from the catalog, `patties add` its components first, then
+generate the listed files — adapting entity names, fields, columns, and copy to
+the user's stated domain (e.g. "a CRM for veterinary clinics").
+
+| Pattern | Goal | `patties add` components | Generated files (under `app/`) |
+|---|---|---|---|
+| **auth-rbac** | Login / logout + role-gated route | `form`, `input`, `label`, `button`, `card` | `routes/login.tsx`, `routes/logout.ts`, `routes/admin.tsx` (role-gated), `lib/auth.ts` (cookie session over mock users), `lib/rbac.ts` (role guard), `lib/mock-users.ts` |
+| **crm** | Contacts list + detail / edit | `data-table`, `dialog`, `form`, `input`, `button`, `badge` | `routes/contacts/index.tsx` (table), `routes/contacts/[id].tsx` (detail), `islands/ContactForm.tsx`, `lib/mock-contacts.ts` |
+| **task** | Task board / list | `card`, `checkbox`, `badge`, `dialog`, `button` | `routes/tasks.tsx`, `islands/TaskBoard.tsx` (columns + toggle), `lib/mock-tasks.ts` |
+| **pivot** | Group-by / pivot over rows | `table`, `select`, `card` | `routes/pivot.tsx`, `islands/PivotTable.tsx` (pick row/col/measure), `lib/mock-rows.ts` |
+| **dashboard** | Metrics overview | `card`, `chart`, `separator`, `sidebar` | `routes/dashboard.tsx` (cards + chart + sidebar shell), `lib/mock-metrics.ts` |
+
+Per-pattern recipes:
+
+- **auth-rbac** — sessions are a signed cookie over the mock user list; the RBAC
+  guard is a small helper the protected route calls in its handler. Make the
+  mock-only nature loud: a banner on the login page and a TODO at the top of the
+  auth module. Real auth needs persistence (a future DB spec).
+- **crm** — the list uses `data-table` over `mock-contacts`; create / edit
+  happens in a `dialog` driven by a `form` island. The detail route reads the
+  same mock store by id.
+- **task** — the board is an island holding `useState` columns; toggling a
+  `checkbox` moves a task between done / not-done. No persistence — state resets
+  on reload (call this out).
+- **pivot** — an island lets the user pick a row dimension, a column dimension,
+  and a numeric measure from `select`s, then renders the aggregated `table`.
+  Aggregation runs client-side over the mock rows.
+- **dashboard** — a static SSR shell (`sidebar` is `subtree`, `chart` hydrates)
+  with metric `card`s fed by `mock-metrics`; the chart is the one interactive
+  island.
+
+Always `patties add` the listed components (initializing the catalog first if
+needed) before generating files that import them. Only reference components that
+exist in the shipped registry with `status: "completed"`.
+
+## Depth contract: UI + mock data
+
+Every pattern is scaffolded at **"UI + mock data"** depth:
+
+- **In scope:** SSR routes / pages, islands where interactivity is needed,
+  stamped Patties UI components, and a typed in-memory seed in
+  `app/lib/mock-<entity>.ts` that the pages read from.
+- **Out of scope:** `bun:sqlite`, migrations, a real persistence or auth
+  backend, network calls. The pattern *shows the shape*; the developer swaps the
+  mock data for a real source later.
+- Every generated `mock-*` module starts with `// TODO: replace mock data with a
+  real source`, and the route / page carries a short note marking the mock
+  boundary.
+
+Do not generate a database layer, migrations, or a real auth/network backend
+from this skill — that is deferred to a future spec.
+
+## Conventions
+
+- Pages live under `app/routes/*.tsx` (default-export a React component); API
+  handlers under `app/routes/api/*.ts` (named `GET`/`POST`/… returning a
+  `Response`, e.g. via `ctx.json()`). Dynamic segments use `[id]`.
+- Islands (interactive client components) live under `app/islands/` and are
+  wrapped at the use site in `<Island name="…">…</Island>` from `patties/render`.
+- Mock data lives in `app/lib/mock-<entity>.ts`, typed, with the TODO marker.
+- Never re-author component source — stamp from the catalog and import.
+
+## See also
+
+- The `patties-cli` skill — running, building, deploying the app.
+- cli specs 11–15 (Patties UI: `ui init`, `add`, `view`, `update`, registries).

package/templates/_codex/.codex/rules/patties-patterns.md

@@ -0,0 +1,105 @@
+# Patties patterns — components & feature scaffolding
+
+> Codex rule. The catalog and recipes below are shared verbatim with the
+> Claude `/patties` skill — both are generated from one source
+> (`templates/_shared/patties-patterns.md` in create-patties), so they
+> cannot drift. Read this when the user asks to add a component or scaffold a
+> feature pattern.
+
+## When to use
+
+Use this when the user wants to **add a Patties UI component** or **scaffold a
+feature pattern** (auth + RBAC, a CRM, a task board, a pivot table, a
+dashboard). It covers scaffolding only — for running, building, deploying, or
+managing secrets, use the `patties-cli` skill instead.
+
+Two capabilities:
+
+1. **Add a UI component** — a thin wrapper over the deterministic catalog.
+2. **Scaffold a feature pattern** — instruction-driven: you generate the files,
+   adapting names/fields/copy to the user's domain.
+
+## Add a component
+
+The component catalog is deterministic — never hand-author component source; the
+registry is the source of truth.
+
+1. If `app/components/ui/_internal/` does not exist, the catalog isn't
+   initialized — run `patties ui init` first (pass `--theme <neutral|slate|stone|zinc>`
+   to match the project).
+2. Run `patties add <name>` (preview first with `patties view <name>` or
+   `patties add --view <name>` if the user wants to see the source).
+3. Import the stamped component from `app/components/ui/<name>.tsx` and use it.
+
+`patties add` edits `package.json` (it never runs an install) and stamps source
+into `app/components/ui/`. After adding, remind the user to run `bun install` if
+new peer deps were added.
+
+## Scaffold a pattern
+
+Pick the pattern from the catalog, `patties add` its components first, then
+generate the listed files — adapting entity names, fields, columns, and copy to
+the user's stated domain (e.g. "a CRM for veterinary clinics").
+
+| Pattern | Goal | `patties add` components | Generated files (under `app/`) |
+|---|---|---|---|
+| **auth-rbac** | Login / logout + role-gated route | `form`, `input`, `label`, `button`, `card` | `routes/login.tsx`, `routes/logout.ts`, `routes/admin.tsx` (role-gated), `lib/auth.ts` (cookie session over mock users), `lib/rbac.ts` (role guard), `lib/mock-users.ts` |
+| **crm** | Contacts list + detail / edit | `data-table`, `dialog`, `form`, `input`, `button`, `badge` | `routes/contacts/index.tsx` (table), `routes/contacts/[id].tsx` (detail), `islands/ContactForm.tsx`, `lib/mock-contacts.ts` |
+| **task** | Task board / list | `card`, `checkbox`, `badge`, `dialog`, `button` | `routes/tasks.tsx`, `islands/TaskBoard.tsx` (columns + toggle), `lib/mock-tasks.ts` |
+| **pivot** | Group-by / pivot over rows | `table`, `select`, `card` | `routes/pivot.tsx`, `islands/PivotTable.tsx` (pick row/col/measure), `lib/mock-rows.ts` |
+| **dashboard** | Metrics overview | `card`, `chart`, `separator`, `sidebar` | `routes/dashboard.tsx` (cards + chart + sidebar shell), `lib/mock-metrics.ts` |
+
+Per-pattern recipes:
+
+- **auth-rbac** — sessions are a signed cookie over the mock user list; the RBAC
+  guard is a small helper the protected route calls in its handler. Make the
+  mock-only nature loud: a banner on the login page and a TODO at the top of the
+  auth module. Real auth needs persistence (a future DB spec).
+- **crm** — the list uses `data-table` over `mock-contacts`; create / edit
+  happens in a `dialog` driven by a `form` island. The detail route reads the
+  same mock store by id.
+- **task** — the board is an island holding `useState` columns; toggling a
+  `checkbox` moves a task between done / not-done. No persistence — state resets
+  on reload (call this out).
+- **pivot** — an island lets the user pick a row dimension, a column dimension,
+  and a numeric measure from `select`s, then renders the aggregated `table`.
+  Aggregation runs client-side over the mock rows.
+- **dashboard** — a static SSR shell (`sidebar` is `subtree`, `chart` hydrates)
+  with metric `card`s fed by `mock-metrics`; the chart is the one interactive
+  island.
+
+Always `patties add` the listed components (initializing the catalog first if
+needed) before generating files that import them. Only reference components that
+exist in the shipped registry with `status: "completed"`.
+
+## Depth contract: UI + mock data
+
+Every pattern is scaffolded at **"UI + mock data"** depth:
+
+- **In scope:** SSR routes / pages, islands where interactivity is needed,
+  stamped Patties UI components, and a typed in-memory seed in
+  `app/lib/mock-<entity>.ts` that the pages read from.
+- **Out of scope:** `bun:sqlite`, migrations, a real persistence or auth
+  backend, network calls. The pattern *shows the shape*; the developer swaps the
+  mock data for a real source later.
+- Every generated `mock-*` module starts with `// TODO: replace mock data with a
+  real source`, and the route / page carries a short note marking the mock
+  boundary.
+
+Do not generate a database layer, migrations, or a real auth/network backend
+from this skill — that is deferred to a future spec.
+
+## Conventions
+
+- Pages live under `app/routes/*.tsx` (default-export a React component); API
+  handlers under `app/routes/api/*.ts` (named `GET`/`POST`/… returning a
+  `Response`, e.g. via `ctx.json()`). Dynamic segments use `[id]`.
+- Islands (interactive client components) live under `app/islands/` and are
+  wrapped at the use site in `<Island name="…">…</Island>` from `patties/render`.
+- Mock data lives in `app/lib/mock-<entity>.ts`, typed, with the TODO marker.
+- Never re-author component source — stamp from the catalog and import.
+
+## See also
+
+- The `patties-cli` skill — running, building, deploying the app.
+- cli specs 11–15 (Patties UI: `ui init`, `add`, `view`, `update`, registries).

package/templates/_codex/AGENTS.md

@@ -15,6 +15,7 @@ Built with Patties — a Bun-native full-stack meta-framework.
 - [Build-time discovery](.codex/rules/build-time-discovery.md) — discovery happens at build time, not at request time.
 - [Optional AI dependency](.codex/rules/optional-ai.md) — keep `@anthropic-ai/sdk` import-disjoint from non-AI code paths.
 - [Patties CLI](.codex/rules/patties-cli.md) — `patties dev / build / start / deploy / secret`.
+- [Patties patterns](.codex/rules/patties-patterns.md) — add UI components and scaffold feature patterns (auth, CRM, task board, pivot, dashboard).
 
 ## Live inventory
 

package/templates/_container/.dockerignore

@@ -0,0 +1,7 @@
+node_modules
+.patties
+.git
+*.log
+Dockerfile
+.dockerignore
+README.md

package/templates/_container/Dockerfile

@@ -0,0 +1,27 @@
+# syntax=docker/dockerfile:1
+# Multi-stage build for a Patties app on the `bun` adapter.
+# Build:  docker build -t {{name}} .
+# Run:    docker run -p 3000:3000 {{name}}
+
+FROM oven/bun:1.3 AS base
+WORKDIR /app
+
+# --- deps: install once, cached on package.json changes ---
+FROM base AS deps
+COPY package.json bun.lock* ./
+RUN bun install
+
+# --- build: produce the production server bundle in .patties/ ---
+FROM base AS build
+COPY --from=deps /app/node_modules ./node_modules
+COPY . .
+RUN bunx patties build --target bun
+
+# --- release: minimal runtime image ---
+FROM base AS release
+ENV NODE_ENV=production
+COPY --from=deps /app/node_modules ./node_modules
+COPY --from=build /app/.patties ./.patties
+COPY package.json ./
+EXPOSE 3000
+CMD ["bun", ".patties/server/server-entry.js"]

package/templates/_monorepo/packages/README.md

@@ -0,0 +1,18 @@
+# packages/
+
+Shared code for this Bun workspace. Create a package per shared concern
+(e.g. `packages/ui`, `packages/db`) with its own `package.json`, then depend
+on it from an app under `apps/*` using the workspace protocol:
+
+```jsonc
+// apps/<app>/package.json
+{
+  "dependencies": {
+    "@{{name}}/ui": "workspace:*"
+  }
+}
+```
+
+Bun resolves `workspace:*` to the local package and runs scripts
+topologically with `bun --filter`. This monorepo is intentionally
+Bun-workspaces-only — no Turborepo / Nx.