PixiJS DOMContainer: HTML overlays on the canvas
Overlay HTML elements (inputs, iframes, videos) on a PixiJS v8 canvas — CSS-transform-driven positioning, anchors, pointer events, EXPERIMENTAL API
- What
- Overlay HTML elements (inputs, iframes, videos) on a PixiJS v8 canvas — CSS-transform-driven positioning, anchors, pointer events, EXPERIMENTAL API
- Cost
- Free
- Needs
- a PixiJS v8 browser 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 skill for `DOMContainer` in PixiJS v8: position any HTML element over the canvas and drive its CSS transform from the scene graph — native inputs, iframes, videos, rich HTML panels that follow a display object's position, with `element` and `anchor` options, visibility sync (hide/remove detaches the element), pointer-events handling (shared root at z-index 1000, decorative overlays should set `pointer-events: none`), and `destroy()` semantics that preserve the element for re-attachment. The default browser bundle auto-registers the DOMPipe; custom builds need the side-effect `import 'pixi.js/dom'`. By @pixijs, listed here with credit to its creator. Honest caveats: marked EXPERIMENTAL in PixiJS v8 — the API may change between minor releases; DOM overlays always render above canvas content (no interleaving with draw calls); `tint`/`filters`/`mask`/`blendMode` have no visual effect on DOM elements — style with CSS; not available in Web Workers; a leaf — never nest PixiJS children inside it; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
PixiJS DOMContainer: HTML overlays on the canvas is a free Muse skill that helps your Muse overlay HTML elements like inputs, iframes, and videos on a PixiJS v8 canvas, with CSS-transform-driven positioning, anchors, and pointer events. Note that this API is marked EXPERIMENTAL in PixiJS v8, so it may change between minor releases.
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 browser project (npm package pixi.js); nothing else — the skill is guidance plus code patterns, no accounts or keys required Install "PixiJS DOMContainer: HTML overlays on the canvas" for me. It teaches an agent @pixijs's official DOMContainer for PixiJS v8: overlay any HTML element (inputs, iframes, videos) on the canvas with scene-graph-driven CSS transforms, element/anchor options, visibility sync, pointer-events handling, destroy semantics that preserve the element, and the pixi.js/dom side-effect import for custom builds — marked EXPERIMENTAL in v8. MIT-licensed. Repository: https://raw.githubusercontent.com/pixijs/pixijs-skills/83760c6f53462ca9cecd68055041f5a8c94758ce/skills/pixijs-scene-dom-container/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-dom-container". 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 an overlay reference; remember the API is EXPERIMENTAL and overlays always sit above canvas content). 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.