create-gametau: make the default Three.js template more game-ready #177
Description
Problem
The default Three.js scaffold generated by create-gametau is intentionally tiny, but today it is so minimal that it stops being a useful game starter. The template sets up a renderer, camera, lights, and a spinning cube, but it does not establish a reusable gameplay-oriented structure.
That means new Three.js projects still have to build the same early boilerplate before they can meaningfully evaluate gametau as a game framework.
Why this matters
- First-run experience strongly shapes whether the Three.js path feels game-ready.
- The current scaffold demonstrates that rendering works, but not how to structure a real game.
- Users still have to hand-roll the same loop/input/assets/camera/disposal setup immediately after scaffolding.
Suggested scope
Keep the template small, but make it opinionated enough to feel like a real starter:
- explicit scene lifecycle and cleanup
- a basic camera rig/pattern appropriate for gameplay work
- asset-loading seam
- input seam
- render/update separation that scales beyond a single mesh
Non-goals
- Building a full engine inside the template
- Shipping genre-specific gameplay
- Replacing the broader scene-layer work
Acceptance criteria
- A new Three.js project starts from a reusable structure rather than a spinning-cube demo.
- The starter shows where rendering, input, assets, and game-loop code belong.
- The template still stays small enough to understand in one read.