PixiJS meshes: custom geometry, MeshPlane, MeshRope, PerspectiveMesh
Custom 2D geometry in PixiJS v8 — MeshGeometry positions/uvs/indices, MeshSimple, subdivided deformation, rope trails and 2.5D perspective corners
- What
- Custom 2D geometry in PixiJS v8 — MeshGeometry positions/uvs/indices, MeshSimple, subdivided deformation, rope trails and 2.5D perspective corners
- 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 skill for custom geometry in PixiJS v8: the base `Mesh` class plus its four specialized subclasses — `MeshSimple` for quick textured shapes with per-frame vertex animation, `MeshPlane` for subdivided textured-rectangle distortion (`verticesX`/`verticesY` control smoothness), `MeshRope` for texture ribbons following a polyline path, and `PerspectiveMesh` for 2D planes with perspective-projected corners (2.5D, not true 3D). Covers hand-built `MeshGeometry` (positions, uvs, indices, topology), when to prefer each variant, batching rules (meshes batch only with `MeshGeometry` and no custom shader — custom shaders always render independently), `shrinkBuffersToFit`, topology-aware `containsPoint` hit testing, and state control via `State.for2d()`. Includes common-mistake callouts: the v8 renames (`SimpleRope`→`MeshRope`, ...) with options-object constructors, and never adding children to a mesh (leaf node — wrap in a `Container`). By @pixijs, listed here with credit to its creator. Honest caveats: for true 3D use a dedicated 3D library; needs the pixijs-scene-core-concepts mental model for the leaf rule; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
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 meshes: custom geometry, MeshPlane, MeshRope, PerspectiveMesh" for me. It teaches an agent @pixijs's official mesh skills for PixiJS v8: the base Mesh plus MeshSimple, MeshPlane (subdivided distortion), MeshRope (texture ribbons on a path), PerspectiveMesh (2.5D corners) — hand-built MeshGeometry (positions, uvs, indices, topology), when to use each variant, batching rules, shrinkBuffersToFit, containsPoint hit testing, state control, and the v8 renames/options-object constructors. MIT-licensed. Repository: https://github.com/pixijs/pixijs-skills/blob/main/skills/pixijs-scene-mesh/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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-mesh". 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 a custom-geometry reference; for true 3D use a dedicated 3D library). 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.