What problem does it solve?
A green build does not prove a game is actually playable. This Skill closes the gap between passing builds and real gameplay quality by combining deterministic test fixtures with short real browser playthroughs, so regressions in controls, saves, and UI feedback are caught before release.
Core Features & Use Cases
- Test Matrix Planning: Maps the full player journey from launch and new game through combat, rewards, saves, pause, settings, and completion, with device variants for desktop, touch portrait, touch landscape, and reduced motion.
- Deterministic Review States: Uses seedable fixtures, debug routes, and query parameters to jump directly to boss phases, inventory loadouts, save migrations, low health, and error states instead of grinding through the campaign.
- Evidence-Based Reporting: Records reproduction steps, expected versus actual results, severity, viewport, and console or performance findings, separating new regressions from pre-existing baseline issues.
- Use Case: Before shipping a WebGL platformer update, run the skill to verify keyboard and touch controls, confirm save/continue works across sessions, check the console for errors on a live scene, and produce an actionable QA report.
Quick Start
Use the test-playable-web-games skill to run an end-to-end playtest of my browser game and report any gameplay regressions with reproduction steps.
