CLI & ecosystem
Beyond this site, the rgbv3d-ecosystem monorepo ships @rgbv3d/core and a CLI for batch encode/decode and benchmarks.
The browser encoder is for spot checks and teaching. CI, album batches, and regression fixtures belong on the CLI. @rgbv3d/core is the shared library: the web bundle and Node CLI share profile definitions and round-trip asserts so behavior does not drift.
Typical flow: run benchmark on fixtures, map your corpus to screenshot / photo / gradient / scan, then decide whether .rgbv3d belongs in an archive script. These commands are not a promise of smaller-than-PNG sizes.
npm run build -w @rgbv3d/core npm run build -w @rgbv3d/cli node packages/cli/dist/index.js encode input.png out.rgbv3d --profile vector-v2 node packages/cli/dist/index.js decode out.rgbv3d restored.png node packages/cli/dist/index.js benchmark ./samples
Relation to the web tool
The /rgbv3d/ page loads a browser build of the same core. If large images fail, downscale or switch to CLI. Privacy boundary matches: pixels are not uploaded to PracticalKit by default.
Source and research notes live under rgbv3d-ecosystem in the PracticalKit repository. Format → · Benchmark →