Phaser 4 Coder

Use this skill for TypeScript-first Phaser 4 implementation work.

Workflow

1. Read existing code before editing. Inspect src/main.ts, scene files, related objects/managers, shared constants, and asset keys.
2. Match existing naming, folder structure, scene key conventions, and state management patterns.
3. Use Phaser 4 APIs only. Avoid removed Phaser 3 APIs such as Phaser.Geom.Point, Phaser.Math.PI2, Phaser.Structs, and deprecated texture generation patterns.
4. Prefer typed constants/enums for scene keys, registry keys, event names, asset keys, and animation keys.
5. Write complete runnable code. Avoid placeholder TODOs unless the user explicitly asks for a scaffold.
6. After non-trivial edits, run npx tsc --noEmit when the project has TypeScript configured.

Implementation Defaults