/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
$ npx -y skills add gamedev-skills/awesome-gamedev-agent-skills --skill pixijs-rendering --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pixijs-rendering
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
pixijs-rendering.SKILL.mdname: pixijs-rendering
description: >
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.
PixiJS 8.19 Rendering
Set up and structure a PixiJS **8.19** application: the async `Application`, asset loading via `Assets`, the `Container`/`Sprite` scene graph, the ticker loop, pointer events, and render groups. Pins the 8.19 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/bundle and load by name. There is no v7 `Loader`. 3. **Build the scene graph.** Everything descends from `app.stage` (a `Container`). Group related objects in `Container`s; child transforms are relative to the parent. Draw order = insertion order (later = on top). 4. **Animate with the ticker.** `app.ticker.add((ticker) => {...})`. Scale motion by `ticker.deltaTime` (frames, ~1 at 60fps) or `ticker.deltaMS` (milliseconds) so speed is frame-rate independent. 5. **Enable events per object** by setting `eventMode = 'static'` (or `'dynamic'`), then `obj.on('pointerdown', ...)`. Federated pointer events cover mouse/touch/pen. 6. **Promote big static subtrees to render groups** (`isRenderGroup: true`) so the GPU caches their transforms. Profile before and after; confirm pixels on screen.
Patterns
1. Async Application boot (the v8 entry point)
import { Application, Assets, Sprite } from 'pixi.js';
(async () => {
// v8: construct empty, then await init(). Config does NOT go in the constructor.
const app = new Application();
await app.init({
background: '#1099bb',
resizeTo: window, // track the window size
antialias: true,
// preference: 'webgpu', // opt into WebGPU; default 'webgl'
});
document.body.appendChild(app.canvas); // v8 uses app.canvas, not app.view
const texture = await Assets.load('https://pixijs.com/assets/bunny.png');
const bunny = new Sprite(texture);
bunny.anchor.set(0.5);
bunny.position.set(app.screen.width / 2, app.screen.height / 2);
app.stage.addChild(bunny);
})();2. Containers for a relative-transform scene graph
import { Container, Sprite } from 'pixi.js';
const world = new Container();
app.stage.addChild(world);
// Children are positioned relative to `world`; move/scale/rotate the whole group
// by transforming the parent.
for (let i = 0; i < 10; i++) {
const coin = new Sprite(coinTexture);
coin.x = i * 40;
world.addChild(coin);
}
world.position.set(100, 100);
world.scale.set(2); // every coin scales with the container3. The ticker loop (frame-rate independent)
let elapsed = 0;
app.ticker.add((ticker) => {
// deltaTime ≈ 1 at 60fps; deltaMS is milliseconds since last frame.
elapsed += ticker.deltaMS;
bunny.rotation += 0.05 * ticker.deltaTime; // smooth at any frame rate
bunny.y = app.screen.height / 2 + Math.sin(elapsed / 500) * 50;
});4. Pointer events (federated)
bunny.eventMode = 'static'; // 'static' = interactive, doesn't move on its own
bunny.cursor = 'pointer';
bunny.on('pointerdown', (event) => {
bunny.tint = 0xff0000;
// event.global is the pointer position in stage space.
});
bunny.on('pointerover', () => bunny.scale.set(1.1));
bunny.on('pointerout', () => bunny.scale.set(1.0));5. Loading many assets by name (bundles)
import { Assets } from 'pixi.js';
await Assets.init({
manifest: {
bundles: [{
name: 'level-1',
assets: [
{ alias: 'hero', src: 'assets/hero.png' },
{ alias: 'tiles', src: 'assets/tiles.png' },
],
}],
},
});
const bundle = await Assets.loadBundle('level-1'); // { hero: Texture, tiles: Texture }
const hero = new Sprite(bundle.hero);6. Render groups for large static layers
// A big, rarely-changing background subtree: let the GPU cache its transforms.
const background = new Container({ isRenderGroup: true });
app.stage.addChild(background);
// Add hundreds of static tiles to `background`. Moving `background` itself stays
// cheap; constantly re-adding/removing children negates the benefit.Pitfalls
- **Blank canvas / "app.stage is undefined"** → you didn't `await app.init()`, or you
configured the constructor. In v8 the constructor is empty; all options go to `init()`.
- **`app.view` is undefined** → v8 renamed it to `app.canvas`.
- **v7 code throwing** → `interactive = true` → `eventMode = 'static'`; `Loader`/
`loader.add` → `Assets.load`; synchronous `new Application({...})` → async `init`.
- **Top-level await build error (Vite ≤6.0.6)** → wrap boot in `(async () => { ... })()`.
- **Speed varies with frame rate** → multiply movement by `ticker.deltaTime` (or use
`deltaMS`); never assume 60fps.
- **Clicks do nothing** → t
Read more
name: pixijs-rendering description: > 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.
PixiJS 8.19 Rendering
Set up and structure a PixiJS **8.19** application: the async `Application`, asset loading via `Assets`, the `Container`/`Sprite` scene graph, the ticker loop, pointer events, and render groups. Pins the 8.19 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/bundle and load by name. There is no v7 `Loader`. 3. **Build the scene graph.** Everything descends from `app.stage` (a `Container`). Group related objects in `Container`s; child transforms are relative to the parent. Draw order = insertion order (later = on top). 4. **Animate with the ticker.** `app.ticker.add((ticker) => {...})`. Scale motion by `ticker.deltaTime` (frames, ~1 at 60fps) or `ticker.deltaMS` (milliseconds) so speed is frame-rate independent. 5. **Enable events per object** by setting `eventMode = 'static'` (or `'dynamic'`), then `obj.on('pointerdown', ...)`. Federated pointer events cover mouse/touch/pen. 6. **Promote big static subtrees to render groups** (`isRenderGroup: true`) so the GPU caches their transforms. Profile before and after; confirm pixels on screen.
Patterns
1. Async Application boot (the v8 entry point)
import { Application, Assets, Sprite } from 'pixi.js';
(async () => {
// v8: construct empty, then await init(). Config does NOT go in the constructor.
const app = new Application();
await app.init({
background: '#1099bb',
resizeTo: window, // track the window size
antialias: true,
// preference: 'webgpu', // opt into WebGPU; default 'webgl'
});
document.body.appendChild(app.canvas); // v8 uses app.canvas, not app.view
const texture = await Assets.load('https://pixijs.com/assets/bunny.png');
const bunny = new Sprite(texture);
bunny.anchor.set(0.5);
bunny.position.set(app.screen.width / 2, app.screen.height / 2);
app.stage.addChild(bunny);
})();2. Containers for a relative-transform scene graph
import { Container, Sprite } from 'pixi.js';
const world = new Container();
app.stage.addChild(world);
// Children are positioned relative to `world`; move/scale/rotate the whole group
// by transforming the parent.
for (let i = 0; i < 10; i++) {
const coin = new Sprite(coinTexture);
coin.x = i * 40;
world.addChild(coin);
}
world.position.set(100, 100);
world.scale.set(2); // every coin scales with the container3. The ticker loop (frame-rate independent)
let elapsed = 0;
app.ticker.add((ticker) => {
// deltaTime ≈ 1 at 60fps; deltaMS is milliseconds since last frame.
elapsed += ticker.deltaMS;
bunny.rotation += 0.05 * ticker.deltaTime; // smooth at any frame rate
bunny.y = app.screen.height / 2 + Math.sin(elapsed / 500) * 50;
});4. Pointer events (federated)
bunny.eventMode = 'static'; // 'static' = interactive, doesn't move on its own
bunny.cursor = 'pointer';
bunny.on('pointerdown', (event) => {
bunny.tint = 0xff0000;
// event.global is the pointer position in stage space.
});
bunny.on('pointerover', () => bunny.scale.set(1.1));
bunny.on('pointerout', () => bunny.scale.set(1.0));5. Loading many assets by name (bundles)
import { Assets } from 'pixi.js';
await Assets.init({
manifest: {
bundles: [{
name: 'level-1',
assets: [
{ alias: 'hero', src: 'assets/hero.png' },
{ alias: 'tiles', src: 'assets/tiles.png' },
],
}],
},
});
const bundle = await Assets.loadBundle('level-1'); // { hero: Texture, tiles: Texture }
const hero = new Sprite(bundle.hero);6. Render groups for large static layers
// A big, rarely-changing background subtree: let the GPU cache its transforms.
const background = new Container({ isRenderGroup: true });
app.stage.addChild(background);
// Add hundreds of static tiles to `background`. Moving `background` itself stays
// cheap; constantly re-adding/removing children negates the benefit.Pitfalls
- **Blank canvas / "app.stage is undefined"** → you didn't `await app.init()`, or you
configured the constructor. In v8 the constructor is empty; all options go to `init()`.
- **`app.view` is undefined** → v8 renamed it to `app.canvas`.
- **v7 code throwing** → `interactive = true` → `eventMode = 'static'`; `Loader`/
`loader.add` → `Assets.load`; synchronous `new Application({...})` → async `init`.
- **Top-level await build error (Vite ≤6.0.6)** → wrap boot in `(async () => { ... })()`.
- **Speed varies with frame rate** → multiply movement by `ticker.deltaTime` (or use
`deltaMS`); never assume 60fps.
- **Clicks do nothing** → t
<img src="docs/assets/banner.png" width="820" alt="awesome-gamedev-agent-skills — game-dev skills for AI coding agents.
Repo: gamedev-skills/awesome-gamedev-agent-skills
Other skills on awesome-gamedev-agent-skills.
- /audio-design
Implement game audio practice — bus/mixer architecture and gain in decibels, ducking (sidechain), adaptive/dynamic music via layering and re-sequencing, SFX variation, and beat synchronization. Engine-neutral. Use when the user mentions audio mixing, audio buses,
Open skill - /camera-systems
Build game cameras that feel good — 2D follow with a deadzone, look-ahead, smoothing, and level-bounds clamping; 3D third-person orbit with collision and first-person look; plus multi-target framing and a shake hook. Engine-neutral techniques that pair with the engine's camera
Open skill - /create-game-assets
Plan, generate, source, normalize, and validate cohesive visual game assets. Use for art direction, style bibles, sprites, tilesets, backgrounds, UI art, icons, textures, concept art, or 3D asset briefs.
Open skill - /dialogue-systems
Build branching dialogue and narrative — a node/choice graph with conditions, variables, and localization hooks — and choose between authoring tools Ink and Yarn Spinner or a custom data-driven runner. Engine-neutral. Use when the user mentions dialogue system, branching
Open skill - /game-ai
Design NPC and enemy decision-making with finite state machines, behavior trees, steering behaviors, and A* pathfinding — engine-neutral algorithms that pair with the detected engine's navigation API. Use when building enemy AI, an FSM or behavior tree, steering/flocking, or
Open skill - /game-feel
Add "juice" and game feel that makes actions satisfying — screen shake, hit-stop/freeze frames, tweened/eased motion, squash & stretch, knockback, and layered audio-visual feedback — as engine-neutral techniques that pair with the detected engine's tween, particle, and camera
Open skill

