# Start here (AI)

1. Read [`../BRIEF.md`](../BRIEF.md) — what to build.  
2. Read [`STACK.md`](STACK.md) completely.  
3. Read [`PACKS.md`](PACKS.md) — you **will** use the medium packs.  
4. Read [`PROMPT.md`](PROMPT.md) non-negotiables.  
5. Copy [`../scaffold/`](../scaffold/) → `../games/<name>/`.  
6. Implement. **Import packs so the path resolves to the URL `/medium/…`** — how many `../` that
   takes depends on your layout, and getting it wrong is a FATAL:
   - `npx devtune init` project (game at `<project>/src/`) → **`../medium/…`**
   - DevTune monorepo (game at `product/games/<name>/src/`) → `../../../medium/…`

   ⚠️ The monorepo path used to be the only one written down. In a `.devtune` install it resolves
   *above your project*, `verify` reports `import-outside-serve`, and the page boots blank.  
7. `node tools/verify.mjs games/<name>` (from `product/`) — includes smoke.  
   Monorepo: `node product/tools/battery.mjs product/games/<name>`.  
8. [`CHECKLIST.md`](CHECKLIST.md) — honest answers.  
9. ⭐ **Read `DEVTUNE-NOTES.md` at the project root, every session.** The human writes into it from
   the desk while playing — press **Notes** in the bottom bar. Each entry is something they noticed
   and did not want to break the session to explain, with the selected thing and the unsaved values
   attached by the tool. It is a work queue: do the items, and delete an entry once it is genuinely
   done. If the file does not exist yet, nothing has been reported.  

Paths in STACK/PACKS that say `born/` mean **this product pack** (`docs/`, `scaffold/`, `medium/`).