Skip to content
cccskills
FreePublished on GitHub

inspect-runtime

Use when reading state from a running PlayCanvas app, to reach its live Application through the Engine devtools hook without changing app code.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.1 KB
  • scripts/devtools-hook.js903 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Inspect a running app

From Engine 2.23, every app announces itself to a hook at globalThis[Symbol.for('playcanvas.inspector')]. Read live state through it instead of adding window.app or debug code to the app.

Attach

  • Resolve scripts/devtools-hook.js relative to this skill and inject it as an init script that runs before any page script. A hook defined later misses existing apps; reload instead.
  • Page code then reads globalThis.__playcanvasApps, a Map from each live app to { version, revision, protocol }. app.init() adds the entry and app.destroy() removes it.
  • The script chains a hook defined before it, such as a devtools extension's.
  • No entry means the Engine predates 2.23, the hook loaded late, or the app set devtools: false. The Engine swallows errors thrown by the hook.
  • In 2.23.0 only the debug build (playcanvas/debug, build/playcanvas.dbg.*) announces apps; the default import never calls the hook. Later 2.23 patches fix every build.

Read state

  • Read after frameend, so values reflect a rendered frame.
  • Return plain numbers and strings to the caller, not Engine objects.
  • Useful reads: app.root.findByName() and findByTag(), world positions and meshInstance.aabb, app.stats.drawCallCount and frameTime, and entity.anim.baseLayer.activeState.
  • Pause with app.timeScale = 0; update still runs with a zero dt. Step one frame by restoring the scale, then zeroing it again on the next frameend.
  • Revert anything you change to take a measurement.

Inspector panel

@playcanvas/inspector adds a panel for people: new Inspector(app) shows the hierarchy, assets, materials, shaders, textures, render targets, frame graph, and physics. It must import the app's own playcanvas package, so add it only to development builds. It draws over the canvas and applies view overrides, so destroy it before verify-pixels captures. Stepping through draws needs the debug build.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.

The English summary is being prepared. Showing the original description.

playcanvas/skills28Updated Oct 13, 2026

Use when writing PlayCanvas Engine code touching transforms, cameras, lights, materials, meshes, bounds, or imports, to apply Engine conventions and avoid legacy APIs.

The English summary is being prepared. Showing the original description.

playcanvas/skills28Updated Oct 13, 2026

Use when composing PlayCanvas entity hierarchies from models, colliders, rigid bodies, and scripts, so each object has one semantic root and clear lifecycle.

The English summary is being prepared. Showing the original description.

playcanvas/skills28Updated Oct 13, 2026

Use when static PlayCanvas lighting, shadows, or ambient occlusion cost too much per frame and should be baked into lightmaps.

The English summary is being prepared. Showing the original description.

playcanvas/skills28Updated Oct 13, 2026

Use when creating or restructuring a PlayCanvas app with the Engine API, @playcanvas/react, or @playcanvas/web-components, covering bootstrap, input, resize, physics, update loop, UI, and lifecycle.

The English summary is being prepared. Showing the original description.

playcanvas/skills28Updated Oct 13, 2026

Use before repeatedly placing GLB models in PlayCanvas to record each asset's uniform scale, grounding offset, pivot compensation, and yaw once.

The English summary is being prepared. Showing the original description.

playcanvas/skills28Updated Oct 13, 2026

See all skills by playcanvas

Report a problem with this skill