# verify-pixels

Shows how to prove a PlayCanvas rendering change leaves the image unchanged, using deterministic captures and pixel comparison.

Skill by PlayCanvas. Category: Testing.

## Install

Project (for this project only):

```sh
npx skills add playcanvas/skills --skill verify-pixels
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add playcanvas/skills --skill verify-pixels -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 203. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/playcanvas/skills/verify-pixels)

## Source

[Open the source](https://github.com/playcanvas/skills/tree/HEAD/skills/verify-pixels). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: verify-pixels
description: Use when a PlayCanvas rendering change is meant to leave the image unchanged, to prove it with deterministic captures and pixel comparison.
---

# 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`.
````

- Previous: [reduce-draw-calls](https://syn4pse.dev/terminal/playcanvas-reduce-draw-calls.md)
- Next: [bake-lighting](https://syn4pse.dev/terminal/playcanvas-bake-lighting.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
