AI Agent Quick Start

Boot.

npx create-cartwright@latest my-site
cd my-site
pnpm dev

create-cartwright installs dependencies, creates the database, and seeds an admin + demo data — the admin login is printed and saved to .admin-credentials. (Manual clone instead? pnpm install && pnpm db:setup && pnpm dev.)

Verify (use your brand.defaultLocale — da in a default scaffold):

curl -s -o /dev/null -w '%{http_code}' http://localhost:3000/da
# expect: 200

Proves: the app boots, the database exists, and the seed ran.

Mint an agent API key (one-time). This unlocks the whole tool surface over REST — POST /api/v1/tools/<name> — without ever opening the admin UI. Keys are normally created in /admin/api-keys; the no-browser bootstrap is a short script that writes the key row directly:

// Run once, then delete (or keep; it only ADDs keys).
import { config as loadEnv } from "dotenv";
loadEnv({ path: ".env" });
loadEnv({ path: ".env.local", override: true });

async function main() {
  const { generateApiKey } = await import("../lib/api-auth");
  const { prisma } = await import("../lib/db");
  const { SCOPES } = await import("../lib/scopes");
  const admin = await prisma.user.findFirst({ where: { role: "admin" } });
  if (!admin) throw new Error("No admin user — run pnpm db:setup first.");
  const { plaintext, hash } = generateApiKey();
  await prisma.apiKey.create({
    data: {
      userId: admin.id,
      name: "agent-bootstrap",
      keyHash: hash,
      scopes: JSON.stringify(SCOPES), // or a narrower list from lib/scopes.ts
    },
  });
  console.log(plaintext); // shown once — the DB stores only the hash
}
main().catch((e) => { console.error(e); process.exit(1); });

KEY=$(pnpm exec tsx --conditions react-server scripts/agent-key.ts | tail -1)

Two caveats that cost a cold agent real minutes when undocumented:

• --conditions react-server is required — the project's lib/* modules guard with server-only.
• Keep the script's imports to exactly this narrow set (lib/api-auth, lib/db, lib/scopes). Importing lib/tools/registry from a standalone script crashes on Next-only modules — call tools over REST instead.

Proves: an admin exists and you now hold a scoped bearer token for the tool API.

Turn on genome copy rendering. The designed looks in step 4 write their pre-written copy through the Resolvable Genome, and the storefront only renders genome copy when the genomeResolve flag is on — without it, only the palette and 3D scene change and the copy silently stays put:

curl -s -X POST http://localhost:3000/api/v1/tools/features.set \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"key":"genomeResolve","enabled":true,"confirm":true}'

Proves: the tool surface works end to end (auth, scopes, confirm-token flow).

Apply a designed look — one call, instant, no LLM involved:

curl -s -X POST http://localhost:3000/api/v1/tools/magic.compose_look \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"vertical":"cafe","confirm":true}'

A Voice (in verticals/: cafe, carpenter, fable, kindergarten, salon) applies pre-written on-brand copy + a palette + a suggested design + a 3D scene in one step. To pick a specific Skin instead or as well, pass "design":"<slug>" (slugs in designs/options.ts) or call design.set_slug.

Proves: the site is designed — copy, palette, layout and scene — without a browser, a designer, or a generation step.

Verify the design landed:

curl -s http://localhost:3000/da | grep -o '<h1[^>]*>[^<]*'

The H1 and the --color-sol-* palette variables in the HTML should reflect the chosen look. That's the finish line: a real, designed, database-backed site serving HTML — at ~99 s on the measured cold run.