develop-web-game

1# Develop Web Game
2 
3Build games in small steps and validate every change. Treat each iteration as: implement → act → pause → observe → adjust.
4 
5## Skill paths (set once)
6 
7```bash
8export SKILLS_ROOT="${WESIGHT_SKILLS_ROOT:-${SKILLS_ROOT:-$HOME/Library/Application Support/WeSight/SKILLs}}"
9export WEB_GAME_CLIENT="$SKILLS_ROOT/develop-web-game/scripts/web_game_playwright_client.js"
10export WEB_GAME_ACTIONS="$SKILLS_ROOT/develop-web-game/references/action_payloads.json"
11```
12 
13Installed skills resolve from `$WESIGHT_SKILLS_ROOT` / `$SKILLS_ROOT` (production default: app `userData/SKILLs`, macOS usually `~/Library/Application Support/WeSight/SKILLs`).
14 
15## Workflow
16 
171. **Pick a goal.** Define a single feature or behavior to implement.
182. **Implement small.** Make the smallest change that moves the game forward.
193. **Ensure integration points.** Provide a single canvas and `window.render_game_to_text` so the test loop can read state.
204. **Add `window.advanceTime(ms)`.** Strongly prefer a deterministic step hook so the Playwright script can advance frames reliably; without it, automated tests can be flaky.
215. **Initialize progress.md.** If `progress.md` exists, read it first and confirm the original user prompt is recorded at the top (prefix with `Original prompt:`). Also note any TODOs and suggestions left by the previous agent. If missing, create it and write `Original prompt: <prompt>` at the top before appending updates.
22…