PixiJS scene graph: containers, leaves, transforms and render order
The PixiJS v8 mental model — container vs leaf, local/world transforms, render groups, culling, masking, RenderLayer and which leaf skill covers which display object
- What
- The PixiJS v8 mental model — container vs leaf, local/world transforms, render groups, culling, masking, RenderLayer and which leaf skill covers which display object
- 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 mental model for the PixiJS v8 scene graph: the tree rooted at `app.stage` as both layout model and render order, the CRITICAL container-vs-leaf distinction (use `Container` for any node that needs children — adding children to a `Sprite`, `Graphics`, `Text` or `Mesh` logs a deprecation warning today and becomes a hard error), how local transforms compose into world transforms (`toGlobal`/`toLocal`), render order by child index with `sortableChildren`/`zIndex` for explicit ordering and `RenderLayer` for order decoupled from hierarchy, render groups (`isRenderGroup`) that move transforms to the GPU for large stable sub-trees, culling with `cullable`/`cullArea`, the four mask types (stencil, alpha, scissor, color), `visible` vs `renderable`, destroy semantics (`children: true`, GPU teardown options), container lifecycle events, the shared constructor-options reference, and a leaf comparison table mapping every display object (Sprite, Graphics, Text, Mesh, ParticleContainer, DOMContainer, GifSprite) to its leaf skill. By @pixijs, listed here with credit to its creator. Honest caveats: framing skill — it frames the pieces and points to the per-leaf deep dives rather than documenting any single API in full; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
PixiJS scene graph is a free Muse skill for the PixiJS version eight mental model. It covers container versus leaf, local and world transforms, render groups, culling, masking and RenderLayer, plus which leaf skill covers which display object. That model helps you structure scenes correctly instead of fighting the renderer.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 83760c6Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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 scene graph: containers, leaves, transforms and render order" for me. It teaches an agent @pixijs's official PixiJS v8 scene-graph mental model: the container-vs-leaf distinction (Container for nodes with children, never nest inside leaves), local/world transform composition, render order with sortableChildren/zIndex and RenderLayer, render groups on the GPU, culling, the four mask types, visible vs renderable, destroy semantics, lifecycle events, the shared constructor-options reference, and the leaf comparison table pointing to each per-leaf skill. MIT-licensed. Repository: https://raw.githubusercontent.com/pixijs/pixijs-skills/83760c6f53462ca9cecd68055041f5a8c94758ce/skills/pixijs-scene-core-concepts/SKILL.md Pinned version: install the code at commit 83760c6f53462ca9cecd68055041f5a8c94758ce exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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-scene-core-concepts". 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 the framing skill; add the per-leaf skills (sprite, graphics, text, mesh) as you need them). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 83760c6 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 11, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.