AutoGineer
Generated banner for Test Playable Web Games
Generated logo for Test Playable Web Games

Test Playable Web Games

Meng ToCommunityCreated by Meng To

  • Skill
  • Review and audit
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Test a playable browser game end to end with deterministic fixtures and real browser evidence. Use for gameplay QA, regression testing, controls, accessibility, responsive/mobile testing, save flows, console checks, performance smoke tests, and release verification.
— the description by Meng To

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a methodology for testing playable web games by combining deterministic test fixtures with real-world browser playthroughs. It emphasizes mapping the player journey, utilizing seedable states to bypass repetitive gameplay, and verifying visual feedback and performance metrics to ensure a consistent user experience across various devices and input methods.

What it does

  • Maps critical player journeys including core actions, inventory management, and save flows.
  • Utilizes seedable fixtures and debug routes to test specific game states directly.
  • Verifies visual feedback and UI responsiveness for player actions.
  • Monitors browser console logs and performance metrics during live scenes.
  • Standardizes the reporting of reproduction steps and evidence for regressions.

When to use it

  • During gameplay QA and regression testing cycles.
  • When verifying accessibility and responsive design across desktop and mobile viewports.
  • To perform performance smoke tests and release verification.
  • When testing complex save flows or specific game state transitions.

Advantages

  • Reduces testing time by using deterministic states instead of manual grinding.
  • Ensures comprehensive coverage across different device and input configurations.
  • Provides actionable evidence by separating new regressions from baseline issues.
  • Improves reliability by verifying both functional logic and visual player feedback.

Usage examples

“Test the inventory save flow for the current build.”
The agent uses a seedable fixture to load a specific inventory state, performs a save action, reloads the game, and verifies the inventory persists correctly.
“Perform a responsive test for the boss encounter on mobile portrait.”
The agent simulates a mobile portrait viewport, triggers the boss encounter via a debug route, and checks for UI clipping or input responsiveness issues.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/mengto/test-playable-web-games/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip test-playable-web-games.zip -d .agents/skills

Documentation by Meng To

Test Playable Web Games

Combine deterministic tests with short real playthroughs. Do not treat a green build as gameplay proof.

Start with a test matrix

Map the player journey: launch, new game, controls, core action, enemy encounter, reward, inventory/progression, save/continue, loss/retry, pause, settings, and completion. Add device variants for desktop keyboard/mouse, touch portrait, touch landscape, and reduced motion.

Prefer deterministic review states

Create seedable fixtures, debug routes, or query parameters for combat phase, inventory loadout, boss phase, tutorial step, save migration, low health, and error states. Test important transitions directly rather than grinding through the campaign.

Verify the player experience

Use the repository-approved browser surface and honor local browser restrictions. Confirm screen-visible feedback after each meaningful action: control response, target state, damage/resource state, UI update, and navigation. Inspect console warnings/errors and sample performance only on a representative live scene.

Report actionable evidence

Record reproduction steps, expected versus actual result, severity, device/viewport, and the shortest useful proof. Separate new regressions from pre-existing baseline issues. After testing, close idle browser pages, dev servers, and benchmarks while leaving active task resources alone.

Files

agents/openai.yaml

interface:
  display_name: "Test Playable Web Games"
  short_description: "Run repeatable browser game playtests"
  default_prompt: "Use $test-playable-web-games to test this playable web game end to end."

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Meng To
Publisher
Meng To (Community)
Source
MengTo/Skills · agent-skills/game-development/test-playable-web-games · commit 5ea1661
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Meng To.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download test-playable-web-games.zip