What problem does it solve? Structuring a Phaser 3 game correctly is hard: developers often misuse scene lifecycles, pick the wrong physics system, load assets at the wrong time, or write frame-dependent logic that breaks across devices. This Skill provides architectural guidance and working code patterns for building maintainable 2D games with Phaser 3. ## Core Features & Use Cases - Scene Architecture: Lifecycle methods (init, preload, create, update), scene transitions, and a recommended Boot/Menu/Game/UI scene structure. - Physics Systems: Guidance on choosing Arcade vs Matter physics, with colliders, overlaps, groups, and body configuration patterns. - Assets, Animation & Tilemaps: Preload patterns with progress bars, spritesheet and atlas animation setup, and Tiled tilemap integration with collision layers. - Anti-Pattern Catalog: Concrete pitfalls to avoid, including spritesheet spacing errors, nine-slice UI slicing mistakes, and frame-dependent movement. - Use Case: Ask the AI to build a platformer prototype, and it will scaffold a Boot scene with a loading bar, a Game scene with Arcade physics, keyboard input, sprite animations, and delta-time movement. ## Quick Start Use the phaser-gamedev skill to create a Phaser 3 platformer scene with a player sprite, gravity, arrow-key movement, and a jumping animation.