phaser

Architect Phaser 3 games with scene-based structure and EventBus communication.

307|37|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/OpusGameLabs/game-creator --skill phaser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phaser
Source: https://github.com/OpusGameLabs/game-creator/tree/main/skills/phaser
Command: npx skills add https://github.com/OpusGameLabs/game-creator --skill phaser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers architect Phaser 3 games with a scalable, convention-driven structure.

Core Features & Use Cases

  • Data-driven project layout with core modules (EventBus, GameState, Constants)
  • Scene lifecycle guidance: init/preload/create/update/shutdown
  • TypeScript-first workflow with Vite templates
  • Best practices for performance, mobile readiness, and clean transitions

Quick Start

Create a new Phaser project scaffold following the conventions described here. Use the official TS + Vite template and integrate the core directories (core/, scenes/, objects/, systems/). Then run the dev server to start prototyping.

Frequently Asked Questions about phaser

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

FAQPage Schema
How do I structure a Phaser 3 game for scalability and state management?

Structure your Phaser 3 game using a convention-driven layout with mandatory directories, centralized game state, EventBus communication, and strict separation of concerns across scene lifecycles. This ensures scalable architecture for new or existing projects.

What is the best way to manage scene transitions and communication in Phaser 3?

Manage scene transitions and communication in Phaser 3 using an EventBus architecture. This pattern decouples scenes via event-driven messaging, ensuring clean transitions and strict separation of concerns throughout the scene lifecycle.

How do I set up a TypeScript and Vite workflow for Phaser 3 game development?

Set up a TypeScript-first Phaser 3 workflow using the official TS and Vite template. Integrate core directories like core/, scenes/, objects/, and systems/, then run the dev server to start prototyping with data-driven configuration.

Can I refactor an existing Phaser project to use a centralized game state and EventBus?

Yes, you can refactor existing Phaser projects to adopt a centralized game state and EventBus communication. This migration applies strict separation of concerns via constants, state, events, and scene lifecycles for a consistent architecture.

Does Phaser 3 scene architecture support mobile readiness and performance best practices?

Phaser 3 scene architecture supports mobile readiness and performance best practices by enforcing data-driven project layouts, clean scene transitions, and strict separation of concerns across init, preload, create, update, and shutdown lifecycles.

When should I not use a centralized EventBus for Phaser game state?

Avoid a centralized EventBus for Phaser game state if your project is a simple prototype where strict separation of concerns, mandatory directories, and data-driven configuration add unnecessary overhead to the scene lifecycle.