hebertzhu 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
- Define a single gameplay goal or bugfix target for the current iteration.
- Make the smallest implementation change that moves the game forward.
- Ensure the game exposes readable state and a deterministic stepping hook when automation depends on them.
- Run the bundled Playwright client after each meaningful change instead of relying on unverified manual play only.
- Review screenshots, text state, and console output together; fix the first real issue, then rerun.
- 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.jsruns the browser test loop for the game.references/action_payloads.jsonprovides 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.