scenes

Manage Phaser 4 scene lifecycle, transitions, and inter-scene messaging.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/arnaudruffin/dvx-phaser-game --skill scenes-arnaudruffin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenes
Source: https://github.com/arnaudruffin/dvx-phaser-game/tree/main/.agents/skills/scenes
Command: npx skills add https://github.com/arnaudruffin/dvx-phaser-game --skill scenes-arnaudruffin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers needing to understand and manage Phaser 4 scenes, including lifecycle, transitions, parallel scenes, inter-scene messaging, and the SceneManager, in a structured guide.

Core Features & Use Cases

  • Understand the full Scene lifecycle (boot, init, preload, create, update, render) and how to coordinate multiple scenes.
  • Learn to orchestrate scene transitions, including starting, stopping, switching, launching in parallel, and waking/sleeping scenes.
  • Master cross-scene communication patterns and data sharing via shared data stores, events, and the ScenePlugin/api.
  • Apply guidance to common games flows (menu + game, HUD overlays, split views) and debugging scenarios.
  • Leverage SceneManager configuration and per-scene settings to control loader, physics, and data injection.

Quick Start

Create two simple scenes (GameScene and UIScene), start one from the other, and observe lifecycle, transitions, and inter-scene messaging.

Frequently Asked Questions about scenes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage the Phaser 4 scene lifecycle and coordinate multiple scenes?

To manage the Phaser 4 scene lifecycle, you orchestrate boot, init, preload, create, update, and render events across multiple scenes. This structured coordination ensures clean transitions and proper scene loading.

What is the best way to handle Phaser 4 scene transitions like parallel launches and switching?

The best way to handle Phaser 4 scene transitions is by using scene operations such as start, stop, pause, sleep, wake, switch, and launch. These operations allow you to run scenes in parallel and manage active states.

How do I pass data and enable cross-scene communication in Phaser 4?

Cross-scene communication in Phaser 4 is achieved via shared data stores, event systems, and the ScenePlugin API. These patterns allow separate scenes to send messages and share game state data seamlessly.

Can I configure per-scene settings for physics and loaders using the Phaser 4 SceneManager?

Yes, you can configure per-scene settings using the Phaser 4 SceneManager and InjectionMap. This allows you to control specific loader configurations, physics setups, and data injection for individual scenes.

How do I structure common game flows like a menu, game, and HUD overlay in Phaser 4?

You structure common game flows in Phaser 4 by applying scene orchestration patterns to menu and game transitions, HUD overlays, and split views. This approach coordinates parallel scenes and manages lifecycle events.

Do I need to understand the InjectionMap to control scene operations in Phaser 4?

Yes, understanding the InjectionMap is necessary to control scene operations in Phaser 4. It allows you to apply per-scene configuration and leverage the SceneManager for precise lifecycle management.