What problem does it solve? Building a browser game iteratively is risky when a broken edit can destroy the last working version and when agents report success without actually verifying the running game. This Skill provides a disciplined loop for developing Babylon.js games inside OpenHarness's Game Viewer, where saves compile into isolated versions and every claim of progress is backed by real checks. ## Core Features & Use Cases - Versioned live preview: The viewer compiles saves into isolated versions, so a broken edit never replaces the last working game, and new versions wait behind a View update prompt without resetting the player's run. - Structured build loop: Track phases (concept, world, play, polish, check) in .harness/progress.json, edit src/, public/, and index.html with Vite asset imports, and run npm run check after every milestone. - Runtime verification bridge: Expose window.harnessGame with setMode, setPaused, restart, and stats(), dispatch a harness:ready event only after the first successful render, and validate the actual viewer state with node "$GODOGEN_TOOLS/check.mjs". - Use Case: Ask the agent to build a 3D exploration game; it shapes the world, wires keyboard controls using event.code, verifies the canvas renders without errors, and finishes with a factual check-phase report. ## Quick Start Use the studio skill to build a small Babylon.js exploration game with a playable character and verify it in the live Game Viewer.
