Use this skill to design, implement, or optimize Phaser 4 asset pipelines.
Workflow
- Identify the asset categories: backgrounds, sprites, animations, UI, atlases, tilemaps, audio, fonts, and generated placeholders.
- Choose the right load method and format for each asset type.
- Decide what belongs in BootScene versus PreloaderScene versus level-specific lazy loading.
- Prefer atlases for many sprites, spritesheets for uniform frame grids, individual images for large single-use art, and paired audio formats where browser support requires it.
- Keep load keys stable and document them in shared constants when the project already uses key registries.
- Include optimization guidance for HTTP requests, GPU texture size, mobile memory, and build output.
Common Outputs
- Asset folder layout
this.load.*calls- Preloader progress UI
- Atlas/spritesheet recommendations
- Audio loading and unlock plan
- Tilemap/Tiled workflow
- Asset budget and optimization checklist
Full Guidance
For the complete asset pipeline playbook, read references/agent-guidance.md. It is copied from the Claude subagent definition but should be applied as a portable skill; ignore Claude-only fields such as model, color, and tools.