develop-web-game

Topics in the source

• Develop Web Game
• Skill paths (set once)
• Workflow
• Test Checklist
• Test Artifacts to Review
• Core Game Guidelines
• Canvas + Layout
• Visuals

Build games in small steps and validate every change. Treat each iteration as: implement → act → pause → observe → adjust. User-scoped skills install under $CODEXHOME/skills (default: /.codex/skills). 1. Pick a goal. Define a single feature or behavior to implement. 2. Implement small. Make the smallest change that moves the game forward. 3. Ensure integration points. Provide a single canvas and window.rendergametotext so the test loop can read state. 4. 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. 5. 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: at the top before appending updates. 6. Verify Playwright availability. Ensure playwright is available (local dependency or global install). If unsure, check npx first. 7. Run the Playwright test script. You must run $WEBGAMECLIENT after each meaningful change; do not invent a new client unless required.

This is an excerpt. Refer to the complete source and its current requirements.