- Home
- Skills
- Game Development
- Game Testing
Works with the AI Agents you already use
Game Testing
Systematic QA and bug-hunting for 2D/3D web games with severity-ranked reporting and logic verification.
Free
About this skill
Game development moves fast, and manual playtesting often misses edge cases in collision math or state transitions. This skill provides a systematic QA framework for 2D and 3D web games, focusing on Three.js and browser-based projects. It transforms vague "does it work?" checks into structured bug reports with evidence-backed findings. ## What it does - **Rule verification** maps game logic against `RULES.md` to identify spec gaps and logic errors. - **Static code review** scans for common pitfalls in game loops, input handling, and entity spawning. - **Automated logic testing** generates unit tests for pure functions like scoring, physics, and state transitions. - **Frame-rate analysis** checks for frame-rate independence across 30, 60, and 144 FPS simulations. - **Deterministic simulation** attempts to reproduce bugs using fixed seeds and scripted inputs. - **Structured reporting** produces severity-ranked bug reports with exact reproduction steps and suggested fixes. ## How it works 1. **Rule Analysis**: The agent reads existing game rules or infers them from the source to establish a testing baseline. 2. **Code Mapping**: It identifies critical paths including the main loop, state machines, and collision logic. 3. **Execution**: The agent runs logic tests and observes behavior for frame-rate issues, input snagging, or memory growth. 4. **Reporting**: Findings are documented in a `BUG_REPORT.md` categorized by severity and impact. ## Frameworks & tools Primary focus on web-based game engines, specifically Three.js and vanilla JavaScript/TypeScript game loops. Works with standard unit testing frameworks for logic validation. ## Why this beats prompting it yourself Generic prompts often miss "feel" bugs like corner snagging or frame-rate dependencies. This skill enforces a rigorous QA checklist covering input focus loss, entity cleanup, and determinism that manual prompting typically overlooks. ## Use cases - **Physics validation** to catch tunneling at high speeds or clipping through geometry. - **State management** to ensure score resets and entity cleanup work perfectly on restart. - **Input stress-testing** to find bugs caused by simultaneous key presses or window resizing. - **Performance audits** to monitor draw call growth or memory leaks during long sessions. ## Known limitations Requires project files to be accessible for code mapping. Playtesting observation is limited to available browser tools or console logs.
Requires access to game source code. Cannot physically "feel" input latency or controller haptics. Deterministic testing requires game support for fixed seeds.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 25 days ago
- Free with an Agensi account
Permissions
File Scopes
Reads the game's source files, writes RULES.md and BUG_REPORT.md, and runs local tests. No network access needed.