Migrate Phaser 3 game projects to Phaser 4 by resolving breaking API changes.
npx skills add https://github.com/Yakoub-ai/phaser4-gamedev --skill phaser-migrate
Please help me install this Agent Skill. Skill: phaser-migrate Source: https://github.com/Yakoub-ai/phaser4-gamedev/tree/main/skills/phaser-migrate Command: npx skills add https://github.com/Yakoub-ai/phaser4-gamedev --skill phaser-migrate
This skill resolves the friction of upgrading game projects from Phaser 3 to Phaser 4 by identifying breaking API changes, behavioral drifts between release candidates, and deprecated features that cause silent failures.
Run the phaser-migrate skill to scan your current project directory for all necessary code updates and configuration changes required for a successful Phaser 4 upgrade.
High-intent search queries and answers about installing and using this skill.
Migrating a Phaser 3 game to Phaser 4 requires identifying breaking API changes, updating dependencies, and adjusting configurations for the Phaser Beam renderer. You must systematically verify geometry, animation, and physics logic for compatibility with Phaser 4 release candidates.
Upgrading to Phaser 4 involves fixing removed classes like Geom.Point and updating deprecated plugins. You also need to correct behavioral drifts between release candidates, such as animation timing and geometry mask issues that cause silent failures.
Yes, updating TypeScript configuration for Phaser 4 is required to ensure your project environment is correctly set up for the new Phaser 4 type system. This prevents compilation errors during the source code refactoring process.
Resolving Phaser 4 animation timing regressions requires applying specific behavioral drift corrections when moving between release candidates. You must target the animation logic directly to restore proper timing functionality affected during the upgrade.
Scanning for deprecated Phaser 3 features is best handled by systematically analyzing your source code for removed classes and outdated plugins. This detects breaking API changes and identifies necessary refactoring for a successful Phaser 4 upgrade.
Geometry mask logic fails silently after upgrading to Phaser 4 due to behavioral drift between release candidates. Correcting these specific regressions requires targeted verification of your geometry logic to ensure compatibility with the latest updates.
ckyeonGuides migration of Phaser 3 projects to Phaser 4.
Dominik-SteinwegIdentify Phaser 3 breaking API changes and provide refactoring instructions for Phaser 4 migration.
Yakoub-aiCompile, validate, and deploy Phaser 4 games with Vite and TypeScript.
ArtRivMaps Phaser 3 APIs and workflows to Phaser 4 equivalents for migration planning and execution.
