# HOW TO USE THESE PROMPTS

Sixteen phases, `PHASE-00` to `PHASE-15`. Run them in order in Claude Code, one per session or one per session block.

## The loop

1. Open Claude Code in the project root. It reads `CLAUDE.md` automatically.
2. Paste the contents of the next `PHASE-XX` file as your message.
3. Let it build.
4. Walk the acceptance criteria yourself. Do not take "done" on trust.
5. Say `commit this phase` when satisfied.
6. Move to the next phase.

## Rules that make this work

**Do not skip ahead.** Phase 8 assumes phases 0 to 7 exist and are working. The prompts are written to be dependent, on purpose, so that each session has a narrow surface.

**Do not run two phases in one session.** The whole point of the split is that Claude Code stays inside a scope it can hold in context. Merging phases is how you get a half-finished checkout.

**Do not paraphrase the prompt.** Paste it whole. The acceptance criteria and the stop conditions are the part that keeps scope from creeping.

**When something is wrong, fix it in that phase.** Do not carry a known bug forward on the promise of a later cleanup phase. There is no cleanup phase.

**When a spec decision turns out to be wrong**, have Claude Code add a numbered entry to `docs/07-DECISION-LOG.md` explaining what changed and why. A silent deviation is worse than a wrong decision, because the next session will not know about it.

## Timeline, rough

Phases 0 to 3 are foundation, roughly a day. Phases 4 to 7 are the storefront, roughly three days. Phases 8 to 11 are commerce and operations, the heaviest block, roughly four days. Phases 12 to 15 are integrations, hardening and launch, roughly two days.

Those numbers assume the product photography and copy exist. If they do not, that is the real critical path, not the code. See open question 16.

## Two things that are not sequential

**Rename early.** The moment the brand name arrives, run `RENAME.md`, whatever phase you are on. It is a find and replace at phase 01 and a data migration at phase 12.

**Staging exists from phase 00.** Phases 12, 13 and 14 verify things that only behave correctly on a real LiteSpeed host: rewrite rules, cache headers, email deliverability, a backup restore. Local is for iteration speed, staging is where those phases are actually signed off.

## Before you start

Answer as many of `docs/10-OPEN-QUESTIONS.md` as you can, especially questions 1 to 8. Every unanswered blocking question means a default gets baked in and revisited later.