Phaser-Assets und Animation

Phaser — assets animation

Use when changing Phaser preload, atlases, tilemaps, sprite animations or streaming.

Version and project gate

Inspect Phaser major version, package lock, scene registry, renderer, scale configuration, Arcade/Matter plugins, loaders, animation keys and deployment base path. Phaser 2 States, Phaser 3 Scenes and newer APIs are not interchangeable. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.

Work

Inventory global texture, cache and animation keys. Define ownership before evicting an asset used by another scene. Validate frame names, atlas dimensions and tilemap references. Publish readiness only after required content loads; keep a recoverable error for missing files.

Deliver

An asset-key inventory and a loading/animation patch with deterministic fallback behavior. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

Repeated animation creation can collide with global keys; a scene restart does not imply cache eviction.

Acceptance scenario

Load a missing atlas, restart a scene sharing textures with an overlay and replay an animation after returning from a menu. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.

Scope and sources

This skill belongs to Kip. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.

• https://docs.phaser.io/phaser/concepts/scenes
• https://docs.phaser.io/api-documentation/class/scene
• https://github.com/phaserjs/phaser/blob/master/skills/physics-arcade/SKILL.md