Scene & Asset Management -- Decision Patterns

Prerequisite skills: unity-foundations/references/prefabs-and-scenes.md (SceneManager API, additive loading), unity-async-patterns (Addressables handle lifecycle, async loading), unity-game-architecture (bootstrap patterns)

These patterns address the most common asset management failures: Claude hardcodes Resources.Load, ignores async loading, and does not account for memory lifecycle.

PATTERN: Scene Architecture Strategy

WHEN: Structuring a project's scenes for a real game (not a prototype)

DECISION:

• Single scene -- Game jam, prototype, tiny game. Everything in one scene. No loading, no complexity. Outgrow it quickly.
• Scene-per-level -- Linear progression (platformers, puzzle games). LoadScene(name, LoadSceneMode.Single) between levels. Clean separation but no shared state without DontDestroyOnLoad.
• Additive scene composition -- Open worlds, persistent HUD, shared systems. A "Boot" or "Persistent" scene stays loaded, gameplay/UI scenes load additively. Most flexible, most complex.