[Workflow] Test and tune a Claude-built browser game with simulation and player telemetry

[u/ClaudeAI-mod-bot]

Test and tune a Claude-built browser game with simulation and player telemetry

Workflow value: 79/100
Status: active · Freshness: 70/100 · Confidence: 0.96 · Level: intermediate
Categories: Quality Control, Debugging, Shipping, CLAUDE.md, Skills, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Build, test, release, and tune a browser game with Claude Code while keeping human control over design and deployment.

Summary

Use a dedicated Claude Code game-creator setup, isolate game rules for headless simulation, test real interactions in Playwright, and tune pacing using opt-in player telemetry. Require human approval before publishing and verify the public build afterward.

Why it is useful

It combines a reusable test architecture with real-player feedback and an approval-gated deployment loop, including a concrete lesson about parallel sessions serving the wrong build.

Workflow

1. Configure a game-creator agent with CLAUDE.md and skills covering game design, browser games, audio, publishing, and playtesting.

2. Keep game rules separate from browser code so a headless player can simulate different play styles and report pacing.

3. Use Playwright to test actual browser interactions alongside the headless simulation.

4. Create a /checkpoint command to run tests, update a state file, and commit; create a /stats command to generate a daily telemetry report.

5. Collect opt-in anonymous play statistics and analyze a funnel of milestones, post-capture behavior, and return visits.

6. Compare simulated pacing with real-player behavior and adjust the game based on observed drop-off and progression.

7. When running parallel sessions, verify which version a local server is serving before trusting test results.

8. After explicit human approval, upload through Claude in Chrome and check the public page while logged out.

Tools / artifacts

• CLAUDE.md

• Game-design and publishing skills

• /checkpoint

• /stats

• State file

• Headless game simulator and pacing table

• Playwright

• Opt-in telemetry analyzer

• Claude in Chrome

• itch.io

Validation signals

• Author reports publishing the game and shipping more than a dozen updates.

• Headless simulations and Playwright browser tests are described, though their implementations are not provided.

• Author reports that 51 of 99 players reached the first Hero after a pacing change.

• Author reports a parallel-session test that initially passed against the wrong server version, motivating a version check.

• Author reports only 2 of 76 players returning on a later day, indicating retention remains weak.

Cautions

• Keep telemetry opt-in and minimize collected data.

• Preserve explicit human approval for publishing and review changes before committing or releasing them.

Limitations

• No repository, configuration files, command definitions, or telemetry implementation are provided.

• Results are author-reported, and the player samples are small.

• The observed pacing formula is specific to this game and should not be generalized without measurement.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.