phaser-gamedev

Build complete Phaser 3 2D games with a staged design-to-polish workflow.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill phaser-gamedev-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phaser-gamedev
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/game/phaser-gamedev
Command: npx skills add https://github.com/notque/vexjoy-agent --skill phaser-gamedev-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents Phaser projects from being built in a fragile, “skip-proof” way by enforcing a staged lifecycle that reliably plans physics, wires scene structure, and avoids common runtime mistakes.

Core Features & Use Cases

  • Phased Construction for Phaser 3 games: Design → Build → Animate → Polish, producing complete 2D gameplay scaffolds instead of partial demos.
  • Physics-first planning (Arcade vs Matter vs none): Selects the appropriate physics engine per game needs and wires it consistently per scene.
  • Production safety gates: Requires measured spritesheet frame dimensions, asset loading in preload(), animation/state-machine correctness, allocation-free update(), and final shippability checks (no debug physics, no stray logs).
  • Game-ready systems: Tilemaps (Tiled integration), spritesheets/atlases, arcade physics tuning, animation state machines, camera effects, particles, tweens, sound, and optional mobile controls.

Quick Start

Use the phaser-gamedev skill to generate a Phaser 3.60+ TypeScript platformer with Arcade physics, a Boot scene loading assets, a controllable player with an animation state machine, tilemap collisions from a Tiled JSON, and polished camera/particle feedback.

Frequently Asked Questions about phaser-gamedev

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

FAQPage Schema
How do I structure a Phaser 3 game to avoid partial demos and ensure shippable code?

To build shippable Phaser 3 games, enforce a staged workflow across design, construction, animation, and polish. This produces complete 2D gameplay scaffolds with reliable physics and scene structure rather than fragile partial demos.

What is the best way to manage spritesheets and animations in a Phaser TypeScript project?

Managing spritesheets in Phaser requires measured frame dimensions and asset loading strictly in the preload() function. Correct animation state-machine transitions ensure allocation-free update loops and reliable gameplay.

How does Phaser Arcade physics compare to Matter physics for 2D game development?

Choosing Arcade or Matter physics depends on your 2D game needs. Physics-first planning selects the appropriate engine and wires it consistently per scene, ensuring correct collisions for platformers, shooters, or top-down RPGs.

How do I integrate Tiled tilemaps with Phaser 3 for platformer collisions?

Integrating Tiled tilemaps in Phaser 3 involves loading the Tiled JSON and wiring tilemap collisions. This creates game-ready systems with controllable players, camera effects, and polished particle feedback for 2D platformers.

Why does my Phaser game loop experience frame drops during animations?

Phaser game loop frame drops often stem from non-allocation-free update loops or incorrect animation state-machine transitions. Ensuring measured spritesheet dimensions and preload-only asset loading prevents these runtime mistakes.

Do I need to remove debug physics from my Phaser game before shipping?

Yes, you must remove debug physics and stray logs before shipping a Phaser game. Final shippability checks require disabling debug physics to ensure the 2D gameplay scaffold is production-ready.