PixiJS Assets: loading, bundles, manifests and caching
Load textures, spritesheets, video, fonts and SVGs in PixiJS v8 — bundles, manifests, background loading, progress and GPU cleanup
- What
- Load textures, spritesheets, video, fonts and SVGs in PixiJS v8 — bundles, manifests, background loading, progress and GPU cleanup
- Cost
- Free
- Needs
- a PixiJS v8 project (npm package pixi.js); nothing else — the skill is guidance plus code patterns, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @pixijs's official skill for the `Assets` API in PixiJS v8: `Assets.init` with basePath, texture preferences or a manifest; `Assets.load` for single, multiple and aliased assets with automatic format detection (textures, SVG, video, spritesheets, web and bitmap fonts, JSON, compressed textures, animated GIFs); feature bundles (`addBundle`/`loadBundle`/`unloadBundle`); background loading for seamless level transitions; progress callbacks with retry/skip/throw load strategies; retina and format switching; per-asset `data` options; and forcing a specific loader with the `parser` field when URLs carry no extension (signed CDN URLs, blob URLs, API endpoints). Includes a decision guide (single image vs bundle vs manifest) and common-mistake callouts — e.g. `Texture.from(url)` no longer fetches in v8, and the positional `Assets.add(key, url)` signature was removed. By @pixijs, listed here with credit to its creator. Honest caveats: loading only — scene usage lives in the companion pixijs-scene-* skills; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a PixiJS v8 project (npm package pixi.js); nothing else — the skill is guidance plus code patterns, no accounts or keys required Install "PixiJS Assets: loading, bundles, manifests and caching" for me. It teaches an agent @pixijs's official Assets API for PixiJS v8: Assets.init with basePath/preferences/manifest, Assets.load with auto-detection (textures, SVG, video, spritesheets, fonts, compressed textures, GIFs), feature bundles, background loading, progress callbacks with retry/skip/throw strategies, resolution/format switching, per-asset data options, and forcing a loader via the parser field for extension-less URLs — plus a decision guide and common-mistake callouts (no Texture.from(url) fetching in v8). MIT-licensed. Repository: https://github.com/pixijs/pixijs-skills/blob/main/skills/pixijs-assets/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "pixijs-assets". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a loading reference; pair it with the pixijs-scene-* skills when building a full game). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.