What problem does it solve? Phaser 4 games are organized around Scenes, but managing their lifecycle states, transitions, parallel execution, and cross-scene communication involves many subtle rules (queued operations, sleep vs shutdown, render ordering) that are easy to get wrong. ## Core Features & Use Cases - Lifecycle Guidance: Covers init, preload, create, and update methods plus all ten scene states from PENDING to DESTROYED. - Multi-Scene Orchestration: Documents start, launch, run, switch, transition, pause, sleep, and render-order control via the ScenePlugin. - Data & Event Communication: Explains six patterns for passing data between scenes, including the global registry and cross-scene event emitters. - Use Case: When building a game with a HUD overlay, use this Skill to correctly launch a UIScene in parallel with the GameScene and wire up score events between them. ## Quick Start Ask how to pause the current Phaser scene and show a pause menu overlay without losing game state.