Project scaffold

Jot a rough brief, then ask your coding agent to draft the PRD with you.

docs/PRD.md has been written.

Read docs/project_start/01-writing-the-prd.md and run the PRD interview. Here's my brief: <paste your brief>

Full walkthrough: docs/project_start/01-writing-the-prd.md.

Three focused Claude Design runs — build the design system, then the prototype, then the handoff docs — each fed the run before it. Paste each run’s prompt at the start of its own session. When you drop the exports into intake/, your coding agent checks them and hands back a fix-list if anything needs re-exporting.

Happens in a Claude Design session — it leaves no trace in the repo, so this page cannot check it.

I've attached my product spec (docs/PRD.md) and the handoff contract (docs/project_start/02-briefing-claude-design.md). Build the design package (the brand system) following the contract's Run 1 export format exactly — especially the Tailwind-native spacing scale and named colour/radius/shadow tokens. Spell the brand-voice rules out explicitly in the package README. Export the package when it's ready.

I've attached the design package you exported in Run 1, my product spec (docs/PRD.md), and the handoff contract (docs/project_start/02-briefing-claude-design.md). Build the product prototype in that brand, following the contract's Run 2 export format — reuse the package's exact token vocabulary, use real on-brand copy, and render the key empty/loading/error states, one .jsx file per screen with matching screenshots and a SCREEN_MANIFEST. Export the prototype when it's ready.

I've attached the design package (Run 1), the prototype (Run 2), and the handoff contract (docs/project_start/02-briefing-claude-design.md). Author the two repo-ready design docs in the shapes the contract's Run 3 section specifies: docs/DESIGN_TOKENS.md (reconciled from the prototype and package tokens) and docs/COMPONENT_SPEC.md (derived from the prototype screens, package atoms, and tokens). Confirm the brand-voice source material is complete.

Full walkthrough: docs/project_start/02-briefing-claude-design.md.

Unzip Claude Design’s whole bundle into the intake/ folder, then ask your coding agent to sort it into the repo and wire it in. It runs a design doctor and hands back a fix-list if the export needs re-doing.

Design tokens, component spec, and the design package are all in place.

Read docs/project_start/03-inserting-the-design.md, sort the bundle I dropped into intake/, and wire in the design.

Full walkthrough: docs/project_start/03-inserting-the-design.md.

Create the Vercel and Supabase accounts and paste the secrets into your .env, then ask the coding agent to finish the wiring.

Supabase credentials found in the environment. Vercel env and GitHub settings are applied outside this build — ask the coding agent to confirm them.

Apply the repo settings and confirm the Supabase connection.

Full walkthrough: README.md#step-4--wire-the-services.

Tell the coding agent your app’s name and one-line description.

The app has a real name in its metadata and package.json.

Name this app "<Your App Name>" — <one-line description>. Update the web metadata and the root package name.

Full walkthrough: README.md#step-5--name-your-app.

Ask the coding agent to write the roadmap from your PRD and prototype.

docs/ROADMAP.md is written and docs/DATA_CONTRACT.md is derived — the build is underway.

Read docs/project_start/04-writing-the-roadmap.md, then write docs/ROADMAP.md for this product, following docs/PRD.md and the prototype in reference/prototype/.

Full walkthrough: docs/project_start/04-writing-the-roadmap.md.