Game Architecture

Workflow

1. Inspect the engine and target platforms. Separate deterministic game rules from rendering, input and persistence.
2. Choose component or entity systems only when their costs fit the game; avoid an engine abstraction without a second consumer.
3. Define update order, save state, scene transitions and lifecycle ownership.
4. Measure frame time and allocation; test rules and state transitions with representative play scenarios.

Completion

Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.

Focused references

• Detailed examples: load only the section relevant to the task.

---

Canonical source: skills/game-development/game-architecture.md.