game-quality-gates

🎮 Game Quality Gates

Stop shipping games with phantom timers, memory leaks, and double-spend exploits. A battle-tested quality standard for H5/Canvas/WebGL games.

💀 The Problem

Every feature works fine alone. They break in combination:

These aren't edge cases — they're the #1 cause of game bugs. After fixing 70+ of these bugs in production H5 games, we encoded the prevention patterns into 12 universal rules.

📋 The 12 Universal Rules

👉 Read full details in the Wiki →

🎯 Engine-Specific Guides

Phaser 3 (Arcade Physics)

• Multi-touch pointer.id tracking (the finger-swap bug)
• physics.pause() ≠ time pause (the phantom timer gotcha)
• OVERLAP_BIAS tuning (3-4 recommended)
• Physics group clear(true, true) between levels

Three.js (WebGL/3D)

• The dispose trio: geometry + material + texture (VRAM leak prevention)
• GLB compression pipeline: 14MB → 800KB (94% reduction)
• gltf-transform prune Skin deletion pitfall on rigged models
• Animation crossfade state machine

Anti-Cheat

• One-time raid tokens (link start → submit)
• Duration + score sanity checks
• Atomic purchase endpoints (no split deduct/grant)

⚡ Install

OpenClaw users:

clawhub install game-quality-gates

Manual:

git clone https://github.com/abczsl520/game-quality-gates.git ~/.openclaw/skills/game-quality-gates

Not using OpenClaw? The wiki is pure knowledge — useful for any game developer. Just read the docs.

✅ Pre-Deploy Checklist (Quick)

🔴 Universal (every game)
  □ New objects in cleanupGameState()?
  □ New timers cancelled in cleanup?
  □ Buffs respected when modifying attributes?
  □ Data cached before destroy()?
  □ Delta time used for movement?
  □ No memory leaks across scenes?
  □ Audio pauses on background?
  □ Purchase has click-lock?
  □ Saves have version + migration?
  □ Network has timeout + fallback?
  □ Asset failure degrades gracefully?
  □ Critical ops server-validated?

🟡 Mobile: multi-touch IDs, iOS audio resume, WeChat WebView compat
🔵 Phaser: clear(true,true), OVERLAP_BIAS, time+physics pause sync
🟣 Three.js: dispose trio, Draco loader, fadeIn/fadeOut transitions

👉 Full checklist with details →

📚 Documentation

📖 Full Wiki →

📁 Skill Structure

game-quality-gates/
├── SKILL.md                    # 12 rules + checklists (auto-loaded by OpenClaw)
└── references/
    ├── phaser.md               # Phaser-specific (loaded on demand)
    ├── threejs.md              # Three.js-specific (loaded on demand)
    └── anti-cheat.md           # Anti-cheat patterns (loaded on demand)

📊 Origin

• Source: Pixel Bounce (像素弹球王) — 70+ bugs across 10 audit rounds
• Source: Tripo 3D Demo (柯基跑酷3D) — GLB compression + animation
• References: Phaser forum best practices, Three.js dispose docs, web game anti-cheat literature (2024-2025)

🔗 Related

• Browser-Use Skill — AI browser automation for OpenClaw
• Bug Audit — Dynamic bug hunting (200+ patterns)
• Debug Methodology — Root-cause debugging
• OpenClaw — The AI agent platform

🔗 Part of the AI Dev Quality Suite

🤝 Contributing

Found a missing pattern? Have engine-specific rules for PixiJS, Babylon.js, or Unity WebGL? Open an issue or submit a PR!

📄 License

MIT — Use freely, attribution appreciated.

⭐ If this saved you from a production bug, star the repo — help other game devs find it!