phaser3-engineer

Build TypeScript-based Phaser 3 games with modular scenes and event-driven communication.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Exia-thd/Digital-Nervous --skill phaser3-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phaser3-engineer
Source: https://github.com/Exia-thd/Digital-Nervous/tree/main/skills/phaser3-engineer
Command: npx skills add https://github.com/Exia-thd/Digital-Nervous --skill phaser3-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building a Phaser 3 web game from scratch requires extensive boilerplate, strict TypeScript setup, disciplined scene architecture, and consistent handling of events, state machines, and object pooling. This skill removes that overhead and delivers a production‑ready, maintainable codebase.

Core Features & Use Cases

  • TypeScript‑First Architecture: Strict typing, separate service layers, and no use of any.
  • Scene Modularity: One file per scene, pure‑logic classes outside scenes, and automatic SRP enforcement.
  • Event‑Driven Communication: Central GameEvents bus for decoupled interactions.
  • Finite State Machines & Pushdown Automata: Reusable FSM base for entities and UI overlays.
  • Object Pooling: Pre‑warmed pools for bullets, enemies, particles, eliminating runtime allocations.
  • Shared Library Integration: Immediate use of VFX, UI, and audio helpers from the common asset‑vfx skill.
  • Anti‑Pattern Guardrails: Detects God Scenes, magic numbers, direct scene references, and any types.

Quick Start

Use the Phaser 3 Engineer skill to generate a complete project scaffold for a platformer game with typed scenes and pooled enemies.

Frequently Asked Questions about phaser3-engineer

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

FAQPage Schema
How do I set up a TypeScript architecture for Phaser 3 HTML5 games?

Set up TypeScript architecture for Phaser 3 by enforcing strict typing, separating service layers, and eliminating `any` types. This approach yields a maintainable, production-ready codebase without extensive manual boilerplate.

What is the best way to structure modular scenes in a Phaser 3 game?

Structure modular scenes in a Phaser 3 game by using one file per scene and keeping pure-logic classes outside scenes. This enforces Single Responsibility Principle (SRP) and prevents anti-patterns like God Scenes.

How do I implement event-driven communication and state machines in Phaser 3?

Implement event-driven communication in Phaser 3 via a central GameEvents bus for decoupled interactions. Pair this with reusable Finite State Machine (FSM) base classes to manage entity behaviors and UI overlays.

How to manage runtime memory allocations for bullets and particles in webgames?

Manage memory in webgames by using pre-warmed object pooling for bullets, enemies, and particles. This technique eliminates runtime allocations, ensuring stable performance during continuous gameplay.

Does Phaser 3 Engineer require Node.js to generate a project scaffold?

Yes, Phaser 3 Engineer requires Node.js, Phaser 3, and TypeScript to build production-grade webgames. It uses these dependencies to generate a complete project scaffold with typed scenes and pooled enemies.