PlayCanvas materials and physics
Separates how an object looks from how it collides and moves. It checks material setup and physics readiness, then assigns transform ownership so visual updates do not fight simulation.
playcanvas-materials-physics
See how it helpsWhen is it useful?
Use when visual models and physical behavior disagree.
What does it help you do?
- Checks the installed rendering backend and physics initialization.
- Separates geometry scale, lighting and transparency from collision setup.
- Defines trigger filters and the owner of physical transforms.
Try asking this
Build a glass obstacle and a collectible ring for our obstacle course. The glass should look transparent but block movement; the ring should trigger collection without blocking. Test before physics finishes initializing and after reset, keeping visible scale and collider size consistent.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
PlayCanvas — materials physics
Use when changing PlayCanvas material/render behavior or integrating collision and rigid-body components.
Version and project gate
Inspect Engine version, Engine-only versus hosted Editor workflow, ESM versus classic scripts, build/export process, asset IDs and tags, render backend, script attributes and target browser requirements. Do not assume a paid Editor service is required for Engine-only work. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Read the selected backend, material API and physics module readiness. Define render/physics transform ownership and geometry scale. Resolve lighting, transparency, collision filters and trigger semantics independently. Keep backend-specific shader examples aligned with the installed engine.
Deliver
A material/physics integration note and minimal representative scene. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A visual model is not automatically a suitable collision mesh; physics module startup is asynchronous in relevant builds.
Acceptance scenario
Load the scene before and after physics readiness, reset a body and compare the asset under the intended light and backend. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Cyra. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md