Game 3D Development

Core Workflow

1. Identify the engine/runtime, target device, input methods, camera style, and performance budget before designing the implementation.
2. Inspect the existing project patterns first: scene graph ownership, update loop, asset loading, physics layer, animation system, ECS/component conventions, and build tooling.
3. Prefer composition for scalable gameplay entities: one script/component has one job, entities "have" capabilities instead of inheriting every behavior from broad base classes, and a small orchestrator coordinates components when needed.
4. Prefer proven engine or library primitives for physics, animation, navigation, collision queries, and asset loading. Hand-roll only when the feature is small, intentionally custom, or the project has no suitable dependency.
5. Build the smallest playable slice that proves camera, controls, collision, feedback, and failure states together.
6. Verify visually and behaviorally. For browser/WebGL projects, use browser screenshots and canvas checks. For engine projects, run the available editor, playmode, unit, or build checks when possible.

Implementation Priorities