game-dev
Game Dev
Turn a game brief into a playable, visually coherent browser game. Keep the game code, deterministic asset processing, builds, and tests local. Use SandBase only for optional generative assets that the user requests.
Read the SandBase API map before generating concept art, textures, sprites, backgrounds, or other AI media.
Establish the build target
Before implementation, resolve only the choices that materially affect the architecture:
- genre, player goal, failure and success conditions;
- input methods and target devices;
- 2D or 3D presentation, camera, aspect ratio, and art direction;
- required mechanics, content scope, and accessibility expectations;
- supplied assets, rights restrictions, target repository, and delivery format.
Inspect the existing project and preserve its framework, package manager, engine, and conventions. For a new project, choose the smallest suitable stack: native canvas or a focused 2D engine for simple 2D games, and a WebGL engine such as Babylon.js for substantial 3D work. Do not replace an established engine merely because another is familiar.