Skip to content
cccskills
FreePublished on GitHub

verify-pixels

Use when a PlayCanvas rendering change is meant to leave the image unchanged, to prove it with deterministic captures and pixel comparison.

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

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Prove pixels unchanged

Choose the gate

  • Byte-exact: the change keeps the same decoded data and the same shading math, so every pixel must match.
  • Side-by-side review: the change alters sampled values, random order, precision, or where math runs. Report it as "not byte-gateable" and show old and new at each pose; do not invent thresholds.

Make frames deterministic

  • Load every asset and match camera, canvas size, lighting, and animation time between builds. Seed incidental randomness.
  • Drive animated shaders from one app-owned time value, not Date.now() or performance.now().
  • app.timeScale = 0 makes dt zero, but update still runs; anything counting frames or reading wall-clock time still advances.
  • Set app.autoRender = false, then app.renderNextFrame = true before each frame to capture.

Capture and compare

  • WebGL: await (device as WebglGraphicsDevice).readPixelsAsync(x, y, w, h, pixels). WebGPU: render into a RenderTarget and read its colorBuffer with Texture#read(). Avoid colour conversion and lossy encoding.
  • Capture the unmodified build twice first. The captures must match exactly, or the harness itself is noisy.
  • Cover every touched surface in at least two poses, plus a mid-animation phase where relevant.
  • Report the count, for example "0 of 65536 pixels differ", or the count and where the differences are. "Looks the same" is not a result.

Keep harness code out of the shipped bundle; attach it through inspect-runtime.

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