Pixijs

Entry point for the PixiJS v8 skill collection. PixiJS is the fastest library available for the web, working across all devices and allowing you to create rich, interactive graphics and cross-platform applications using WebGL, WebGPU, and Canvas as a fallback.

dean-stack integration (read before mounting Pixi inside a component)

PixiJS is first-party in dean-stack at pixi.js@^8.18.1 for any canvas-based UI. It is a side channel the same way anime.js is — render functions stay pure; everything that touches Pixi (new Application(), Ticker.add(...), sprite mutation, scene-graph reads) lives inside useEffect / useLayoutEffect / event handlers, never during render.

The canonical lifecycle wrapper is usePixiApp(canvasRef, setup, deps) in apps/<name>/app/canvas/use-pixi-app.ts:

• Owns async Application.init({ canvas, resizeTo, preference: "webgl", autoStart: options.autoStart ?? !reducedMotion }).
• Calls the user setup(app, { reducedMotion }) callback once init resolves; the callback registers children and Ticker tasks and may return a cleanup function.
• Tears down on unmount via app.destroy(true, { children: true, texture: true }), with cancellation that survives StrictMode double-mount.
• Detects prefers-reduced-motion: reduce once at mount and passes it to setup; callers must skip Ticker registration when true (static frames still render).
• Static scenes that only update on resize or pointer input should pass autoStart: false and call app.render() from those handlers.
• React owns the <canvas> DOM node; Pixi only paints into it. The wrapping component renders <canvas ref={canvasRef}> inside a sized container.

Pillar mapping (same constraints as the rest of the stack):

• Pillar 1 (Storybook-first) — every Pixi-wrapping component ships with a sibling *.stories.tsx and a Playwright story spec.
• Pillar 2 (Zod-first types) — Pixi-wrapping component props are still z.object schemas wrapped by defineComponent. Pixi-internal types (Texture, Container, etc.) are runtime-only and don't need Zod validation.
• Pillar 3 (IDB-first state) — game state (progress, score, settings) stays in atomWithIDB. Pixi DisplayObjects never own data; they read derived values via refs the React component updates from atom subscriptions.
• Pillar 4 (CLI-gate-first) — Pixi component story specs run in the Playwright storybook project under headless Chromium. WebGL via SwiftShader is reliable; the default preference: "webgl" in usePixiApp keeps tests deterministic.

Seed example: apps/web/app/components/pixi-canvas-demo/ (and the same in the generator template) — a rotating square that demonstrates Ticker registration, reduced-motion short-circuit, and the canvas-ref-as-Pixi-canvas pattern.

How to use this skill

1. Find the specialized skill in the router below that best matches the task.
2. Load that skill's SKILL.md and follow its guidance.
3. If no sub-skill fits (the task references a specific class, function, option, or API surface not listed below), WebFetch https://pixijs.download/release/docs/llms.txt. That file is the auto-generated, always-current index of the full PixiJS API and guides. Each entry links to a .html.md page you can WebFetch for the detailed content.

For the long-form description and trigger keywords of every skill, see references/index.md.

Skill router

Foundations

Scene Objects

Utilities

Advanced

Fallback: canonical PixiJS docs

If the task references a class, function, option, or API surface not covered by any sub-skill above, WebFetch https://pixijs.download/release/docs/llms.txt. It's the auto-generated index of the full PixiJS API and guides, regenerated on every release. Each entry links to a .html.md page you can WebFetch for the detailed content. Use this fallback whenever the router table doesn't point at an obvious match.