What problem does it solve? Setting up a new Phaser 4 game requires navigating dozens of GameConfig options across renderer selection, canvas placement, scale modes, and frame rate settings, with subtle interactions (like pixelArt overriding antialias) that cause silent misconfiguration. ## Core Features & Use Cases - Renderer and Boot Configuration: Choose between AUTO, CANVAS, WEBGL, and HEADLESS renderers and understand the full boot sequence from config parsing to the game loop. - Scaling and Canvas Setup: Apply scale modes (FIT, RESIZE, EXPAND), centering, zoom constants, and parent DOM placement for responsive or fixed-aspect layouts. - Pixel Art and FPS Tuning: Enable pixelArt or smoothPixelArt rendering and configure fps limits, smoothing, and timeout fallbacks. - Use Case: When starting a new browser game, use this Skill to generate a complete GameConfig with WebGL rendering, FIT scaling centered in a container, and a 30 FPS cap, while avoiding gotchas like fps.target not enforcing frame rate. ## Quick Start Create a new Phaser.Game config for a pixel art game that fits a 320x240 canvas centered in the page with 2x zoom.