PlayCanvas profiling and delivery
Checks the exported game rather than relying on the editor preview. It separates script, drawing and pixel costs and verifies resource paths and compressed assets in the delivered environment.
playcanvas-profiling-delivery
See how it helpsWhen is it useful?
Use when Editor preview works but the published game stalls or misses content.
What does it help you do?
- Separates JavaScript allocation, draw submission and pixel costs.
- Checks production paths and compressed resource availability.
- Compares one scoped optimization on representative devices.
Try asking this
Our exported kart game loads in the editor but loses scenery on the website. Inspect production asset paths and compressed files, then measure a crowded race on a representative device. Fix one observed bottleneck and compare the same route, recording the exact tested build.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
PlayCanvas — profiling delivery
Use when diagnosing PlayCanvas startup, GPU/JS cost, memory or exported-browser failures.
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
Measure the representative play route and actual device. Separate JS allocations, draw submission, pixel cost and asset requests. Check exported paths, compressed assets and script dependencies in a production build. Compare one scoped optimization without arbitrary universal draw-call targets.
Deliver
A bottleneck record and reproducible export/browser handover. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
An Editor preview does not establish exported asset availability or production performance.
Acceptance scenario
Load the exported app from its real base path, repeat a level transition and replay a busy scene with a constrained graphics device. 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