What problem does it solve? Visual QA of an HTML5 game requires reaching specific in-game states and capturing them faithfully, which is tedious and error-prone when done manually through a headed browser. ## Core Features & Use Cases - Static state screenshots: Drive the game to a target state via the DEV-only window.__qa play API, pause the loop, settle one frame, and capture a lossless screenshot. - Short recordings: Record the canvas with MediaRecorder, split the clip into frames with ffmpeg, build a contact sheet, and pull a lossless PNG candidate. - Forced rare states: Jump directly to late unlocks, low-probability outcomes, or win/lose screens that a short natural playthrough cannot reach. - Use Case: Before merging a UI change, capture before/after screenshots of every menu, core-loop screen, and unlock panel to audit the visual diff. ## Quick Start Ask the AI to start the dev server and capture a headless screenshot of the game's main menu and combat screen using the capture-game-states skill.