shipshit-engine

The architecture that EVERY studio game shares. Imperative Three.js for the game, React + Tailwind only for the HUD/menu shell. This is the skeleton @shipshitgames/engine will encode; the proof implementation is scourge-survivors (cited throughout). Read those files before writing — match them exactly.

The three pillars

1. Game — a thin orchestrator. Constructs the GameContext + the GameSystems registry, runs the requestAnimationFrame loop, and exposes the public API by delegating to systems. It holds almost no logic of its own.
2. GameContext — the shared mutable world. Anything touched by more than one system lives here (renderer, scene, camera, controls, clock, raycaster, collision arrays, entity pools, current map, status/outcome). State owned by a single system stays private on that system. Constructed with (container, listener).
3. GameSystems — a registry interface. Each system is new XSystem(ctx, sys) and calls siblings via this.sys.<name>. Construction order is irrelevant. The interface uses type-only imports so there is no runtime import cycle.

File layout