What problem does it solve? Automated or agent-driven playtesting of a Pixi'VN game fails when calling narration functions directly, because steps expect the app's live StepLabelProps (navigate, t, toast). This Skill teaches how to enable and drive the Game.testing devtools bridge on window so external scripts can play the game exactly like a real player. ## Core Features & Use Cases - Browser-based game control: Start labels, continue steps, select choices, answer input prompts, go back, and close labels through window.pixiVN. - Live props and action routing: setProps injects the app's real StepLabelProps, and setActions routes testing calls through the app's own UI functions so agent actions match real player behavior. - State control and error capture: Seed or assert storage, snapshot/restore full game state, and collect errors raised during automated runs. - Use Case: An AI agent starts the game at label "start", reads getState() to see open choices, selects choice 0, seeds storage with gold: 100, and verifies the shop unlocks — all as a headless regression test. ## Quick Start Enable Game.testing in dev mode, then ask the agent to start the game at the start label and play through the story by reading getState and calling continue or selectChoice on window.pixiVN.
