hatch-pet

To create a Codex-compatible animated pet spritesheet, provide reference concept images or generated art to run a script-driven assembly workflow. This generates a full 192x208 cell sprite atlas in an 8x9 grid layout, enforcing deterministic prompts and strict transparency rules for a ready-to-ship asset.

Codex pet sprite atlases require a specific grid layout of 8x9 cells, with each cell measuring 192x208 pixels. This strict format ensures consistent pet identity across frames and compatibility with the Codex app's expected directory structure.

You package and validate pixel art spritesheets by running a script-driven workflow that assembles the final pet package. It outputs a pet.json file and a spritesheet.webp file, applying strict transparency rules and deterministic QA-ready packaging under Codex's expected directory layout.

Yes, you can use generated images, screenshots, character art, or visual references to build a Codex pet sprite atlas. The workflow automates creation, verification, and packaging from these inputs to ensure deterministic and consistent pet identity across animation frames.

The Codex pet spritesheet workflow requires the Pillow Python library to process images and assemble the final atlas. This dependency handles the strict transparency rules and image manipulation needed to export the spritesheet.webp file.

Codex pet spritesheet validation fails when strict transparency rules or the 192x208 cell grid layout are not met. The script-driven workflow enforces these deterministic constraints to guarantee the final pet.json and spritesheet.webp files are QA-ready for Codex embedding.