pixijs-rendering
Build a PixiJS v8 render layer: create the async Application, load textures with Assets, compose the scene graph with Container and Sprite, drive the ticker loop, wire pointer events, and group draws with render groups. Use when building or debugging PixiJS v8 — when the user mentions PixiJS, Pixi, Application, app.stage, Container, Sprite, Assets.load, app.ticker, or eventMode. Pins the v8 async init() API.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill pixijs-rendering --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PixiJS v8 Rendering Set up and structure a PixiJS **v8** application: the async `Application`, asset loading via `Assets`, the `Container`/`Sprite` scene graph, the ticker loop, pointer events, and render groups. Pins the v8 API (async `init`, unified `Assets`, `eventMode`). ## When to use - Use when starting a PixiJS v8 project, fixing a blank canvas, structuring the display list, loading textures, animating via the ticker, or handling pointer input. - Use when `package.json` depends on `pixi.js` (v8) and code does `import { Application } from 'pixi.js'`. **When *not* to use:** Phaser's scene/loader model → `phaser-core`. 3D scenes → `threejs-scene-setup`. PixiJS v7-and-earlier code (synchronous `new Application({...})`, `Loader`, `interactive = true`) needs the v8 migration first; this skill targets v8 only. ## Core workflow 1. **Create and `await` the Application.** In v8, `new Application()` is empty; configuration happens in `await app.init({...})`. Append `app.canvas` (not `app.view`) to the DOM. Wrap top-level `await` in an async function for bundlers. 2. **Load assets with `Assets`.** `await Assets.load(url)` returns a `Texture`. For many assets, register a manifest/bundl
- When to use
- Core workflow
- Patterns
- 1. Async Application boot (the v8 entry point)
- 2. Containers for a relative-transform scene graph
- 3. The ticker loop (frame-rate independent)
- 4. Pointer events (federated)
- 5. Loading many assets by name (bundles)
- 6. Render groups for large static layers
- Pitfalls
- References
- Related skills
What does the pixijs-rendering skill do?
Build a PixiJS v8 render layer: create the async Application, load textures with Assets, compose the scene graph with Container and Sprite, drive the ticker loop, wire pointer events, and group draws with render groups. Use when building or debugging PixiJS v8 — when the user mentions PixiJS, Pixi, Application, app.stage, Container, Sprite, Assets.load, app.ticker, or eventMode. Pins the v8 async init() API.
How do I install it?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill pixijs-rendering --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gamedev-skills/awesome-gamedev-agent-skills, a repository with 406 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.