Configuration

Every scaffold saves a .coldstart.json at the project root. This file captures all configuration options and enables deterministic regeneration via coldstart replay.

Complete example

Here is a realistic full-stack configuration:

{
  "name": "fittrack",
  "displayName": "FitTrack",
  "description": "A fitness tracking app with workout plans, nutrition, and social features",
  "packageScope": "@fittrack",
  "platforms": ["web", "mobile", "api"],
  "webMode": "landing+app",
  "domain": "health",
  "billing": "freemium",
  "billingProvider": "polar",
  "i18n": true,
  "locales": ["en", "fr"],
  "multiTenant": false,
  "rbac": false,
  "oauthProviders": ["google", "apple"],
  "outputDir": "./fittrack"
}

Schema reference

Project identity

Platforms

Features

Context

Constraints

The Zod schema enforces the following constraints at validation time. Invalid configs are rejected with clear error messages.

Validation

The config is validated using a Zod schema (projectConfigSchema). Validation happens in all commands that read a config: init, create, replay, setup, and add.

When validation fails, the CLI prints each issue with its field path and message:

✖  Invalid configuration:
  → webMode: webMode is required when platforms includes web
  → multiTenant: multiTenant must be enabled for per-seat billing

Validation runs .refine() checks after basic type validation, so you get all type errors first, then constraint errors. The exit code is 1 on any validation failure.

Platforms

Web modes

Billing models

All billing models generate:

• packages/db/src/billing-schema.ts — Drizzle schema for billing data
• apps/api/src/routes/webhooks.ts — Webhook handler for the chosen provider
• apps/api/src/middleware/billing.ts — Route protection middleware
• Provider-specific client helpers (Polar SDK or Stripe SDK)
• Web billing pages (if web platform present)
• Mobile billing integration via RevenueCat (if mobile platform present)

Default values

When using coldstart create with natural language inference, or when fields are omitted in interactive mode, these defaults apply:

Generated AI context

Every project gets three AI integration points, conditional on the platforms and features selected:

The skills and MCP servers are conditional. A web-only project gets Vercel + Tailwind + React skills. A fullstack project with mobile and billing gets everything including RevenueCat, Expo, and Drizzle skills.

The domain field injects industry-specific guidelines into CLAUDE.md that steer all AI-assisted development toward best practices for that domain (e.g., money-as-integers for finance, HIPAA awareness for health, cursor-based pagination for social).