What problem does it solve? Verifying that a gameplay feature actually works requires playing the running game, not just reading code or trusting that an action call succeeded. This Skill gives an AI agent a disciplined loop for driving the live Summer Engine game — launching deterministically, probing state and screenshots before and after each action, stepping exact frames, and asserting real changes with frame-number evidence. ## Core Features & Use Cases - Deterministic launches: Start the main game or up to three offscreen instances with pinned seeds and fixed frame rates for reproducible runs and side-by-side A/B comparisons. - Frame-stamped evidence: Use summer_game_probe to capture the live node tree, property values, and a screenshot atomically per frame, then compare before/after probes to prove motion, spawning, or state changes. - Scripted and recorded input: Drive the game with timed synthetic input scripts, or record real input to res://.summer/replays/ and replay it on a deterministic instance for regression checks. - Use Case: After implementing a jump feature, launch an offscreen deterministic instance, probe the player's position at frame N, script a jump input, step exactly 30 physics frames, probe again at frame N+30, and assert the vertical velocity changed — citing both frame numbers as proof. ## Quick Start Playtest the current game by launching a deterministic offscreen instance, probing the player state before and after a scripted move_right input, and report the frame-stamped position change.
