AI accelerates typing, not observability. Treat debugging as a first-class skill: log with intent, reproduce with scripts, and refuse “it works on my laptop” as a closing statement.
Build a reproduction recipe
For every bug: URL, browser + version, steps, expected vs actual, console trace. Paste that into your assistant—models solve faster with receipts.
DevTools habits
- Performance panel for rAF spikes.
- Network throttling before blaming “lag.”
- Mobile emulation then a real device pass.
Deterministic seeds
Wire a ?seed=123 query or debug overlay to replay RNG-heavy levels. Screenshots from the same seed should match—if not, you have nondeterminism to hunt.
Automated checks that pay rent
- Unit tests for scoring and inventory rules.
- Smoke test that boots the game and clicks start.
- Lint to catch undefined vars introduced by giant diffs.
Table: bug classes common in AI prototypes
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Works once then blank | Event listener duplication | Teardown on scene change |
| Drift on Safari | 100vh quirks | Use dvh or measure container |
| Desync multiplayer | Full state spam | Throttle + authoritative server |
FAQ
Should AI write tests? Let it draft—you pick invariants worth locking.
When is logging enough? Until you have paying players or tournaments—then metrics.
Next steps
- Browse vibe-coded games for polish references.
- Compare assistants in AI tools.
YGG Play publishes reliability guides for fast-moving indies.
