develop-web-game

name	develop-web-game
description	Use when building or iterating on a web game and you need a tight implement-test-observe loop; prefer the bundled Playwright client, inspect screenshots and text state, and validate every meaningful change before moving on.

Develop Web Game

Intent

• Use for browser-based game development loops where each iteration needs implementation, automated interaction, screenshot review, and state inspection.

Default operating pattern

1. Define a single gameplay goal or bugfix target for the current iteration.
2. Make the smallest implementation change that moves the game forward.
3. Ensure the game exposes readable state and a deterministic stepping hook when automation depends on them.
4. Run the bundled Playwright client after each meaningful change instead of relying on unverified manual play only.
5. Review screenshots, text state, and console output together; fix the first real issue, then rerun.
6. Keep a running progress log so another agent can pick up the loop without losing the current target or pending bugs.

Bundled helpers

• scripts/web_game_playwright_client.js runs the browser test loop for the game.
• references/action_payloads.json provides example input bursts for the client.

Pack fit

• Included in: automation-and-testing
• Useful for repeatable game QA and bugfix loops, not just one-off visual checks.

Boundary

• Do not declare a game change done without re-running the automated interaction loop.
• Do not rely on screenshots alone if text state or console output shows a conflicting failure.