What problem does it solve? Managing Phaser 4 game scenes involves a complex lifecycle (init, preload, create, update), state transitions, and cross-scene communication that is easy to get wrong, leading to stale references, broken restarts, and incorrect render ordering. ## Core Features & Use Cases - Scene Lifecycle Management: Covers all ten scene states from PENDING to DESTROYED, including init, preload, create, and update methods with correct data flow. - Multi-Scene Orchestration: Start, stop, pause, sleep, wake, switch, and transition between scenes, plus run parallel scenes like a UI overlay on top of gameplay. - Cross-Scene Communication: Pass data via start parameters, the global registry, scene-specific data managers, or event emitters between decoupled scenes. - Use Case: Build a game with a GameScene and a parallel UIScene where collecting coins in the game emits events that update the score display in the UI layer. ## Quick Start Ask the AI to create a Phaser scene with init, preload, create, and update methods, then add a parallel UI scene that listens for score events.