Profile first, optimize second. This covers the full PixiJS v8 performance toolkit: proper destroy patterns (including the critical `cacheAsTexture(false)` before destroying cached containers), GC tuning, PrepareSystem for preloading GPU resources, object pooling instead of create/destroy churn, and batching rules that actually matter. The cacheAsTexture section is solid on tradeoffs (GPU memory vs draw calls, the 4096px limit, when not to cache). Culling gets a mention but leans on the core-concepts skill for depth. The batching examples show why draw order matters more than most people think. If you're hitting FPS issues or memory leaks in a PixiJS app, start here and follow the destroy cleanup patterns religiously.
npx skills add https://github.com/pixijs/pixijs-skills --skill pixijs-performance