What problem does it solve? Building a 2D browser game from scratch involves dozens of architectural decisions—scene structure, state management, physics, input handling, and performance optimization—that beginners often get wrong, leading to memory leaks, broken restarts, and unmaintainable code. ## Core Features & Use Cases - Enforced Architecture Conventions: Mandates a core/ directory with an EventBus singleton, centralized GameState with reset(), and a Constants file so games stay restart-safe and free of magic numbers. - Complete Implementation Patterns: Provides reference guides for scenes and lifecycle, game objects, object pooling, Arcade vs Matter.js physics, state machines, texture atlases, and mobile-first input with touch controls. - Asset-Free Visual Polish: Includes procedural design techniques—gradients, parallax layers, particles, screen shake, and spectacle events—so games look polished without any image assets. - Use Case: A game jam participant asks the AI to create a mobile-friendly endless runner; the Skill scaffolds a Vite + TypeScript Phaser project with Boot/Preloader/Game/GameOver scenes, pooled obstacles, touch and keyboard input, and a pre-ship validation checklist. ## Quick Start Create a new Phaser 3 game where the player taps to jump over obstacles, with score tracking and a clean restart on game over.