PROMPT A GAME: instructions for Claude (the coding agent)
=========================================================

A person wants to make a party game for a shared screen: the game runs on a big screen, every phone is a
controller (tilt direction plus up to four buttons). They gave you this address so you can fetch the tools
and build it. They may know nothing about programming. Do all the terminal work yourself, explain in plain
words, and never ask them to type a command.

1. THE SKETCH. Look at the attached sketch and the description. If there is no sketch, ask for a photo or a
   short description of: what the big screen shows, what the phone has (buttons, tilt), how you win.
   Ask at most three short questions, only about things you cannot sensibly decide yourself.

2. NODE. Run `node -v`. Version 20 or newer is needed. If it is missing, say so and ask before installing
   (on a Mac: `brew install node` if Homebrew exists, otherwise send them to https://nodejs.org).

3. THE KIT. In the current folder (an empty folder is ideal):
       curl -L -o kit.zip https://promptagame.org/download/prompt-a-game-starter.zip
       unzip kit.zip && rm kit.zip
   That gives a folder `prompt-a-game-starter` with three siblings inside: `my-game`, `screen-space-time`
   and `gyro-controller`. Keep them side by side. Work only inside `my-game`; do not edit the two tools
   unless asked.

4. READ, THEN INSTALL. In `my-game`: run `npm install`. Then read `AGENTS.md` in `my-game`, and what it points
   to: `node_modules/@sndrv/screen-space-time/AGENTS.md` and `README.md`. They explain how a sketch becomes
   a game (the phone page is built in; you write `public/game.js` and `server.js`).

5. CHECK THE EXAMPLE FIRST. Run `npm start` in the background and tell the person it works before you change
   anything. Then build their game in small steps (something that moves first, then the rest). Keep it
   playable after every step.

6. TELL THEM HOW TO PLAY, in plain words:
   - Big screen: open http://localhost:8080/ in a browser on this computer, full screen, click once on it
     for sound.
   - Phones: same Wi-Fi; open the https address the big screen shows. The phone warns about the certificate
     the first time (iPhone: "visit this website"; Android: "Advanced, Proceed"). That is normal: the computer
     made its own certificate. Then enter a name, tap JOIN, allow motion, hold the phone upright and tilt.
   - No phones to hand: `npm run bots` adds pretend players.
   - If tilting does nothing: the phone is on an http:// address; it needs https.

7. THEN ITERATE. Ask what they felt when playing ("too fast", "can't see the score") and adjust.

RULES THAT SAVE HOURS
- Every URL in `public/` is relative (`game.js`, `./_sst/screen.js`), never starting with `/`.
- No bundler, no extra dependencies. Plain ES modules in the browser.
- The big screen is authoritative: simulate the game in the browser; the server only relays input.
- Never put secrets in the project folder. Do not publish or upload anything unless asked.
- Games for this site only use the phones' tilt and buttons, and run on the person's own computer.

Made by Prompt a Game, https://promptagame.org/