Loading...
Loading...
Found 20 Skills
Verify and release Three.js browser games. Combines playtest QA, automated bot playtests, mobile/responsive checks, production builds, preview verification, static-hosting base paths, debug gating, bundle review, screenshots, visual test harness decisions, packaged canvas-pixel inspection with measured metrics, console checks, and release risk reports.
This skill should be used when the user asks to "playtest my game", "test my Phaser game", "does my game actually run", "check the game in a browser", "verify the game works", "smoke test the game", "automate game testing", "catch black screens", "check for asset 404s", "measure FPS", "screenshot the game", "write a playtest scenario", or whenever Phaser 4 code has been written or changed and needs runtime verification before being handed back to the user.
Building interactive experiences that engage, challenge, and delight playersUse when "game, gamedev, game development, phaser, unity, unreal, godot, gameplay, game loop, sprites, collision, physics, player, level, tilemap, games, gamedev, interactive, gameplay, physics, engines, performance, player-experience" mentioned.
Building interactive experiences that engage, challenge, and delight playersUse when "game, gamedev, game development, phaser, unity, unreal, godot, gameplay, game loop, sprites, collision, physics, player, level, tilemap, games, gamedev, interactive, gameplay, physics, engines, performance, player-experience" mentioned.
Pre-Production validation — build a production-quality end-to-end build to confirm the full game loop is achievable before committing to Production. Run after GDDs, architecture, and UX specs are complete. Produces a PROCEED/PIVOT/KILL verdict that gates the Pre-Production → Production transition.
Design, implement, tune, or test Three.js action-game encounters. Use for arena layout, enemy composition, spawn pacing, objectives, boss phases, reward cadence, encounter fixtures, and difficulty validation.
Concept prototype — validate the core idea is worth designing before writing GDDs. Run right after /brainstorm and /setup-engine. Routes to HTML, Engine, or Paper path based on game type. Produces a throwaway build and a PROCEED/PIVOT/KILL verdict.
Shape level flow, pacing, navigation, encounter staging, and spatial teaching.