What problem does it solve? Deciding where game assets should live (local files vs. remote hosting), how to register them so code can reference them safely, and when to load them without causing visible stalls is a recurring source of bugs in Pixi'VN projects. This Skill provides the exact conventions and file locations for managing assets correctly. ## Core Features & Use Cases - Local vs. online asset strategy: Explains when to keep files in src/assets (processed by PixiJS AssetPack into public/assets with an auto-generated manifest) versus hosting them on a CORS-enabled CDN, GitHub raw, or cloud storage. - Manifest and bundle registration: Shows the single edit point (src/assets/index.ts) for adding online assets, and how to name bundles after label ids, route paths, or character ids. - Loading strategy: Covers Assets.init, blocking vs. background bundle loading at startup, per-label via Game.onLoadingLabel, and per-route via router loaders. - Use Case: You need to add a background music track hosted on a CDN and a set of local character sprites. This Skill tells you to drop the sprites into src/assets, register the CDN URL as an alias in src/assets/index.ts, and background-load the audio bundle at startup. ## Quick Start Use the pixi-vn-assets skill to register my hosted background music and local character sprites in the assets manifest and set up bundle loading at startup.
