hatch-pet · diff
git:20260506.f253260 to git:20260512.c25113b
347 added, 130 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: hatch-pet
- description: Create, repair, validate, preview, and package Codex-compatible animated pets and pet spritesheets from character art, screenshots, generated images, or visual references. Use when a user wants to hatch a Codex pet, create a custom animated pet, or build a built-in pet asset with an 8x9 atlas, transparent unused cells, row-by-row animation prompts, QA contact sheets, preview videos, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.
+ description: Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.
---
# Hatch Pet
## Overview
- Create a Codex-compatible animated pet from a concept, one or more reference images, or both. This skill owns pet-specific prompt planning, animation rows, frame extraction, atlas geometry, QA, previews, and packaging. It delegates visual generation to `$imagegen`.
+ Create a Codex-compatible animated pet from a concept, brand cue, company/prospect name, one or more reference images, or any combination of those inputs. This workflow keeps the deterministic hatch-pet pipeline for atlas geometry, validation, visual QA, and packaging, while using concise state-specific prompts and allowing any pet-safe visual style.
- User-facing inputs are optional. If the user omits a pet name, infer one from the concept or reference filenames; if that is not possible, choose a short appropriate name. If the user omits a description, infer one from the concept or references. If the user omits reference images, generate the base pet from text first, then use that base as the canonical reference for every animation row.
+ User-facing inputs are optional. If the user omits a pet name, infer one from the concept, brand, company, or reference filenames; if that is not possible, choose a short friendly name. If the user omits a description, infer one from the concept or references. If the user omits reference images, generate the base pet from text first, then use that base as the canonical reference for every animation row.
## Generation Delegation
Use `$imagegen` for all normal visual generation.
Before generating base art, row strips, or repair rows, load and follow the installed image generation skill:
```text
${CODEX_HOME:-$HOME/.codex}/skills/.system/imagegen/SKILL.md
```
- Do not call the Image API directly for the normal path. Let `$imagegen` choose its own built-in-first path and its own CLI fallback rules. If `$imagegen` says a fallback requires confirmation, ask the user before continuing.
+ Do not call the Image API, image CLI, or any other image-generation path directly. Let `$imagegen` choose its own built-in-first path and fallback rules. If `$imagegen` says a fallback requires confirmation, ask the user before continuing.
- When invoking `$imagegen` from this skill, pass the generated pet prompt as the authoritative visual spec. Do not wrap it in the generic `$imagegen` shared prompt schema and do not add extra polish, hero-art, photo, product, or illustration-style augmentation. Pet prompts should stay terse, sprite-specific, and digital-pet oriented; only add role labels for input images and any essential user constraint.
+ When invoking `$imagegen`, pass the generated pet prompt as the authoritative visual spec. Pet prompts should stay concise, state-specific, sprite-production oriented, and grounded in the listed input images. Keep longer policy and QA rules in this skill and the deterministic review scripts rather than expanding them into every image prompt. Do not wrap prompts in the generic `$imagegen` shared prompt schema.
- Use this skill's scripts for deterministic work only: preparing prompts and manifests, ingesting selected `$imagegen` outputs, extracting frames, validating rows, composing the final atlas, creating QA media, and packaging.
+ Use this skill's scripts for deterministic image work only: preparing layout guides and prompts, mirroring approved `running-left`, extracting frames, validating rows, composing the final atlas, and creating contact-sheet plus motion-preview QA media. Parent-owned shell/`jq` steps handle manifest updates, packaging, and cleanup.
- Hard boundary: do not create, draw, tile, warp, mirror, or synthesize pet visuals with local Python/Pillow scripts, SVG, canvas, HTML/CSS, or other code-native art as a substitute for `$imagegen`. For a normal pet run, expect up to 10 visual generation jobs: 1 base pet plus 9 row-strip jobs. The only exception is `running-left`, which may be derived by mirroring `running-right` only after `running-right` has been generated, visually inspected, and explicitly approved as safe to mirror. If mirroring is not appropriate, generate `running-left` as a normal grounded `$imagegen` row. If those calls are too expensive, blocked, or unavailable, stop and explain the blocker instead of fabricating row strips locally.
+ ## Storage Controls
- Do not mark visual jobs complete by editing `imagegen-jobs.json`, copying files into `decoded/`, or writing helper scripts that populate row outputs. Use `record_imagegen_result.py` for selected built-in `$imagegen` outputs, or `generate_pet_images.py` only for the documented secondary fallback. The deterministic scripts may only process already-generated visual outputs.
+ The built-in `$imagegen` path stores generated PNG bytes in the rollout that invokes it, even when it also writes a file under `${CODEX_HOME:-$HOME/.codex}/generated_images`. Deleting files later reduces filesystem use, but it does not shrink an already-written rollout. Keep image generation isolated and bounded:
- Only the base job may be prompt-only. Every row-strip job generated through `$imagegen` must use the input images listed in `imagegen-jobs.json`, including the canonical base reference created after the base job is recorded. Treat any row generation without attached grounding images as invalid.
+ - Use one lightweight generation worker per visual job. Do not batch multiple base/row jobs into the same worker.
+ - Workers must return only `selected_source=...` and `qa_note=...`; they must not include Markdown image previews, base64, or extra visual attachments in their final response.
+ - The parent must not open every generated PNG visually. Use worker QA for each job and inspect only the final contact sheet.
+ - After copying the selected generated output into `decoded/`, remove the selected original from `${CODEX_HOME:-$HOME/.codex}/generated_images` when it lives there, then remove its now-empty generation directory if possible.
+ - For storage-sensitive full runs, ask the user whether to use the `$imagegen` CLI fallback when available. That path requires local API credentials and explicit user confirmation, but it can avoid built-in image payloads being embedded in rollout events.
- ## Codex Digital Pet Style
+ ## Brand Discovery
- Default pet art should match the Codex app's built-in digital pets: small pixel-art-adjacent mascots with compact chibi proportions, chunky readable silhouettes, thick dark 1-2 px outlines, visible stepped/pixel edges, limited palettes, flat cel shading, simple expressive faces, and tiny limbs. Even if the reference art is more detailed, complex or realistic, the generated pet should be simplified into this style.
+ If the user provides a brand, company, product, or prospect name rather than a concrete avatar description or reference image, run a lightweight discovery subagent before preparing the pet run. The discovery worker must use web search and prefer official sources such as the brand site, product pages, docs, about pages, press pages, or brand pages. Use reputable secondary sources only when official pages are too thin. Keep the search narrow: enough to extract visual and personality cues, not a market-research brief.
- Do NOT generate polished illustration, painterly rendering, anime key art, 3D rendering, glossy app-icon treatment, realistic fur or material texture, soft gradients, high-detail antialiasing, and complex tiny accessories. References that are more detailed than this should be simplified into the house style before row generation.
+ Skip discovery when the user already provides a concrete mascot/avatar description or reference images, unless the user explicitly asks for brand research.
+ Discovery worker responsibilities:
+
+ - search the web for 2-4 relevant sources, preferring official pages
+ - write an adaptive markdown brief rather than a rigid field dump
+ - cover identity/category, audience/use context, visual system, personality/tone, product/domain motifs, mascot translation cues, avoidances, and evidence/confidence
+ - mark mascot guidance that is inferred from sources as inference
+ - avoid copying logos, readable marks, UI screenshots, slogans, or text
+ - end with a compact `Generation handoff` section containing only `brand_name`, `brand_brief`, `avatar_seed`, `avoid`, and `brand_sources`
+ - do not generate images, prepare run folders, or edit unrelated files
+
+ Use this discovery worker prompt:
+
+ ```text
+ Research a brand for hatch-pet mascot creation.
+
+ Brand/product/prospect: <brand name>
+ User context: <short user request>
+ Output file: <absolute path to brand-discovery.md>
+
+ Use web search. Prefer official brand, product, docs, about, press, or brand pages. Use reputable secondary sources only if official sources are too thin. Write an adaptive markdown brief to the output file. Headings may flex by brand, but the brief must cover:
+ - identity/category: canonical name, product type, what it does
+ - audience/use context: who it serves and where it appears
+ - visual system: palette, shapes, line quality, materials, typography feel, iconography, patterns
+ - personality/tone: emotional traits, energy, formality, playfulness
+ - product/domain motifs: objects, workflows, verbs, metaphors, environments
+ - mascot translation cues: candidate forms, signature traits, props, what must read at pet size
+ - avoidances: logos/text, trademark-sensitive elements, misleading cues, competitor confusion, poor mascot fits
+ - evidence/confidence: source URLs plus notes where evidence is weak or inferred
+
+ Do not copy logos, readable marks, UI screenshots, slogans, or text. Clearly label mascot guidance that is inferred rather than directly sourced.
+
+ End the brief with a `Generation handoff` section containing exactly:
+ - brand_name=<canonical brand/product name>
+ - brand_brief=<one sentence, max 45 words, covering palette/tone/domain motifs/personality>
+ - avatar_seed=<short mascot-safe visual idea, no logo copying>
+ - avoid=<short comma-separated list>
+ - brand_sources=<comma-separated source URLs>
+
+ Return exactly:
+ brand_discovery_file=<absolute output file path>
+ brand_name=<canonical brand/product name>
+ brand_brief=<same compact sentence from Generation handoff>
+ avatar_seed=<same short seed from Generation handoff>
+ avoid=<same short avoid list from Generation handoff>
+ brand_sources=<same comma-separated URLs from Generation handoff>
+ ```
+
+ The parent should save the markdown brief before preparing the run, then pass it to `prepare_pet_run.py` as `--brand-discovery-file` together with `--brand-name`, `--brand-brief`, repeated `--brand-source`, and a concise `--pet-notes` value based on `avatar_seed` when the user did not provide a better avatar description. Keep the full brief for review; only the compact handoff fields should shape prompts. If web search is unavailable and the user gave only a bare brand name, ask for brand cues before generating.
+
+ For a normal pet run, expect up to 10 visual generation jobs: 1 base pet plus 9 row-strip jobs. The Codex app contract currently uses all 9 states: `idle`, `running-right`, `running-left`, `waving`, `jumping`, `failed`, `waiting`, `running`, and `review`. The only deterministic visual derivation is `running-left`, which may be produced by mirroring `running-right` only after `running-right` has been generated, visually inspected, and explicitly approved as safe to mirror. If mirroring is not appropriate, generate `running-left` as a normal grounded `$imagegen` row.
+
+ After selecting a visual output, the parent agent copies that exact image into the job's `decoded/` path and marks the job complete in `imagegen-jobs.json`. Do not write helper scripts that populate row outputs. The deterministic Python scripts may only process already-generated visual outputs.
+
+ Only the base job may be prompt-only. Every row-strip job generated through `$imagegen` must use the input images listed in `imagegen-jobs.json`, including the canonical base reference created after the selected base output is copied. Treat any row generation without attached grounding images as invalid.
+
+ ## Pet-Safe Styles
+
+ Default style is `auto`: infer the pet's style from the user's prompt and references, then preserve that style across every row. If the user names a style, honor it. Supported style presets include `pixel`, `plush`, `clay`, `sticker`, `flat-vector`, `3d-toy`, `painterly`, `brand-inspired`, and `auto`.
+
+ Any style is acceptable when it remains pet-safe:
+
+ - compact whole-body silhouette readable inside a `192x208` cell
+ - consistent face, proportions, material, palette, and props across all rows
+ - clean removable chroma-key background
+ - details large enough to read at pet size
+ - no text, labels, UI, or readable logos unless the user explicitly provides approved reference art and asks for them
+
+ Non-pixel styles are first-class. Plush, clay, sticker, vector, 3D toy, painterly mascot, ink, and brand-inspired looks should be accepted when they satisfy the atlas and readability constraints.
+
## Transparency And Effects
- Pet rows are processed into transparent 192x208 cells, so every generated pixel must either belong to the pet sprite or be cleanly removable chroma-key background. Prefer pose, expression, and silhouette changes over decorative effects.
+ Pet rows are processed into transparent `192x208` cells, so every generated pixel must either belong to the pet sprite or be cleanly removable chroma-key background. Prefer pose, expression, and silhouette changes over decorative effects.
+ The deterministic raster pipeline owns the transparency invariant: pixels that become fully transparent are normalized so they do not retain hidden RGB residue, and atlas validation should fail if exported files violate that invariant. Do not paper over colored halos or transparent-pixel residue by accepting visually inconsistent outputs.
+
Allowed effects must satisfy all of these conditions:
- The effect is state-relevant and helps explain the animation.
- The effect is physically attached to, touching, or overlapping the pet silhouette, not floating nearby.
- The effect is inside the same frame slot as the pet and does not create a separate sprite component.
- - The effect is opaque, hard-edged, pixel-style, and uses non-chroma-key colors.
- - The effect is small enough to remain readable at 192x208 without clutter.
-
- Examples of allowed effects: a tear touching the face, a small smoke puff touching the box or head, or tiny stars overlapping the pet during a failed/dizzy reaction.
+ - The effect is opaque, hard-edged enough for clean extraction, and uses non-chroma-key colors.
+ - The effect is small enough to remain readable at `192x208` without clutter.
Avoid these by default because they usually break transparent-background cleanup or component extraction:
- wave marks, motion arcs, speed lines, action streaks, afterimages, blur, or smears
- detached stars, loose sparkles, floating punctuation, floating icons, falling tear drops, separated smoke clouds, or loose dust
- cast shadows, contact shadows, drop shadows, oval floor shadows, floor patches, landing marks, impact bursts, glow, halo, aura, or soft transparent effects
- text, labels, frame numbers, visible grids, guide marks, speech bubbles, thought bubbles, UI panels, code snippets, checkerboard transparency, white backgrounds, black backgrounds, or scenery
- chroma-key-adjacent colors in the pet, prop, effects, highlights, or shadows
- stray pixels, disconnected outline bits, speckle/noise, cropped body parts, overlapping poses, or any pose that crosses into a neighboring frame slot
State-specific guidance:
- - `idle`: keep this calm and low-distraction. Use only subtle breathing, a tiny blink, a slight head/body bob, a very small material sway, or another quiet persona-preserving motion. Do not show waving, walking, running, jumping, talking, working, reviewing, emotional reactions, large gestures, item interactions, or new props.
- - `waving`: show the wave through paw pose only. Do not draw wave marks, motion arcs, lines, sparkles, or symbols around the paw.
+ - `idle`: keep this calm and low-distraction. Use only subtle breathing, a tiny blink, a slight head or body bob, a very small material sway, or another quiet persona-preserving motion. The loop must still contain visible micro-variation; do not accept six effectively identical copies. Do not show waving, walking, running, jumping, talking, working, reviewing, emotional reactions, large gestures, item interactions, or new props.
+ - `waving`: show the wave through paw, hand, wing, or limb pose only. Do not draw wave marks, motion arcs, lines, sparkles, symbols, or floating effects around the gesture.
- `jumping`: show vertical motion through body position only. Do not draw shadows, dust, landing marks, impact bursts, bounce pads, or floor cues.
- `failed`: tears, attached smoke puffs, or attached stars are allowed if they obey the allowed-effects rules; do not use red X marks, floating symbols, detached smoke, detached stars, or separate tear droplets.
- - `review`: show focus through lean, blink, eyes, head tilt, or paw position. Do not add magnifying glasses, papers, code, UI, punctuation, or symbols unless that prop already exists in the base pet identity.
- - `running-right` and `running-left`: show directional locomotion through body, limb, and prop movement only. Do not draw speed lines, dust clouds, floor shadows, or motion trails.
- - `running`: show an active working/in-progress loop, as if the pet is busy running a task. Do not show literal foot-running, jogging, sprinting, treadmill motion, raised knees, long steps, pumping arms, or directional travel.
-
- ## Pet Naming
-
- Ask the user for a pet name when they have not provided one and only if the conversation naturally allows it. If asking would slow down a direct execution request, choose a short appropriate name from the pet concept, reference image, or personality, then use that name consistently as the display name and as the source for the package folder slug.
-
- Good built-in style examples:
-
- - Codex - The original Codex companion.
- - Dewey - A tidy duck for calm workspace days.
- - Fireball - Hot path energy for fast iteration.
- - Rocky - A steady rock when the diff gets large.
- - Seedy - Small green shoots for new ideas.
- - Stacky - A balanced stack for deep work.
- - BSOD - A tiny blue-screen gremlin.
- - Null Signal - Quiet signal from the void.
+ - `waiting`: show that Codex needs approval, help, or user input through an expectant asking pose. Keep it distinct from ordinary idle and review.
+ - `running`: show active task work, processing, thinking, scanning, typing, or focused effort. Do not show literal foot-running, jogging, sprinting, treadmill motion, raised knees, long steps, pumping arms, directional travel, speed lines, dust clouds, floor shadows, motion trails, or detached motion effects.
+ - `review`: show focus through lean, blink, eyes, head tilt, or paw/hand position. Do not add magnifying glasses, papers, code, UI, punctuation, symbols, or other new props unless they already exist in the base pet identity.
+ - `running-right` and `running-left`: show directional drag movement through body, limb, and prop movement only. `running-right` must face and travel right; `running-left` must face and travel left. Their cadence must visibly alternate across the loop rather than repeating one nearly static stride. Do not draw speed lines, dust clouds, floor shadows, motion trails, or detached motion effects.
## Visible Progress Plan
For every pet run, keep a visible checklist so the user can see where the work is up to. Create the checklist before starting, keep one step active at a time, and update it as each step finishes.
- Before creating the checklist, establish the pet name when possible. Use the user-provided name when available; otherwise infer a short appropriate name from the concept or references. If the name is too long, not settled, or not appropriate for a friendly checklist, use `your pet` instead.
-
Use this checklist for a normal pet run, replacing `<Pet>` with the pet's name or `your pet`:
1. Getting `<Pet>` ready.
2. Imagining `<Pet>`'s main look.
3. Picturing `<Pet>`'s poses.
4. Hatching `<Pet>`.
What each step means:
- - `Getting <Pet> ready.` Choose or confirm the pet name, description, source images, and working folder.
- - `Imagining <Pet>'s main look.` Generate the pet's main reference image. This is required for new pets, even when the user does not provide an image, because it becomes the visual source of truth.
- - `Picturing <Pet>'s poses.` Create the pose rows, starting with `idle` and `running-right` to confirm the pet still looks consistent. Only mirror `running-left` if `running-right` clearly works when flipped.
- - `Hatching <Pet>.` Turn the approved poses into the final pet files, review the contact sheet, previews, and validation results, fix any broken parts, save `pet.json` and `spritesheet.webp` into the pet folder, then tell the user where the pet and QA files were saved.
+ - `Getting <Pet> ready.` Choose or confirm the pet name, description, source images, style preset, style notes, and working folder. For bare brand/product/company requests, first run the brand discovery worker and capture the compact brand brief, source URLs, and avatar seed.
+ - `Imagining <Pet>'s main look.` Generate the pet's main reference image. This becomes the visual source of truth.
+ - `Picturing <Pet>'s poses.` Generate pose rows through lightweight workers, starting with `idle` and `running-right` to confirm identity and gait. Only mirror `running-left` if `running-right` clearly works when flipped.
+ - `Hatching <Pet>.` Turn the approved poses into final pet files, review the contact sheet, previews, and validation results, fix any broken parts, save `pet.json` and `spritesheet.webp`, then report the output paths.
- Only mark a step complete when the real file, image, or decision exists. If this is just a repair run, start from the first relevant step instead of restarting the whole checklist.
+ Only mark a step complete when the real file, image, or decision exists. If this is a repair run, start from the first relevant step instead of restarting the whole checklist.
## Default Workflow
1. Prepare a pet run folder and imagegen job manifest:
```bash
SKILL_DIR="${CODEX_HOME:-$HOME/.codex}/skills/hatch-pet"
python "$SKILL_DIR/scripts/prepare_pet_run.py" \
--pet-name "<Name>" \
--description "<one sentence>" \
--reference /absolute/path/to/reference.png \
--output-dir /absolute/path/to/run \
--pet-notes "<stable pet description>" \
- --style-notes "<style notes>" \
+ --brand-discovery-file /absolute/path/to/brand-discovery.md \
+ --brand-name "<optional researched brand name>" \
+ --brand-brief "<optional compact researched brand cue sentence>" \
+ --brand-source "https://example.com/source" \
+ --style-preset auto \
+ --style-notes "<optional freeform style notes>" \
--force
```
All arguments above are optional except any flags needed to express user constraints. For text-only requests, pass the concept through `--pet-notes` and omit `--reference`; `prepare_pet_run.py` will infer a name, description, chroma key, and output directory as needed.
+ For brand-only requests, run the discovery worker first, save the markdown brief, then pass the brief path through `--brand-discovery-file`, `avatar_seed` through `--pet-notes`, `brand_name` through `--brand-name`, `brand_brief` through `--brand-brief`, and each source URL through repeated `--brand-source`.
- 2. Inspect the next ready `$imagegen` jobs:
+ 2. Inspect `imagegen-jobs.json` for the next ready `$imagegen` jobs. A job is ready when its `status` is not `complete` and every id in `depends_on` is already complete. Prefer reading the manifest directly with `jq` or the editor instead of adding helper scripts for status display:
```bash
- python "$SKILL_DIR/scripts/pet_job_status.py" --run-dir /absolute/path/to/run
+ jq '.jobs[] | {id, kind, status, depends_on, prompt_file, retry_prompt_file, input_images, output_path, derivation_policy}' /absolute/path/to/run/imagegen-jobs.json
```
- 3. For each ready job, invoke `$imagegen` with:
+ 3. Generate visual jobs with lightweight workers by default:
- - the prompt file listed in `imagegen-jobs.json`
- - every input image listed for the job, with its role label
- - the default built-in `image_gen` path unless `$imagegen` itself routes otherwise
+ - Generate and copy `base` first, using a lightweight base worker.
+ - Generate and copy `idle` and `running-right` next as the identity and gait check, using one lightweight worker per row.
+ - Inspect `running-right`; mirror `running-left` only when visual identity, prop placement, markings, lighting, and direction semantics remain correct.
+ - Generate `running-left` normally with a lightweight worker when mirroring would change meaning or identity.
+ - Generate the remaining rows with lightweight workers, using every input image listed for each job.
- The base job must complete first. If user references exist, the base job uses them. If no references exist, the base job may be prompt-only. After recording the base, `record_imagegen_result.py` writes `decoded/base.png` and `references/canonical-base.png`; all row jobs use the original references if present plus those canonical base images.
+ For each ready visual job, invoke `$imagegen` with the prompt file listed in `imagegen-jobs.json`, every listed input image with its role label, and the default built-in `image_gen` path unless `$imagegen` itself routes otherwise. The parent agent must keep its own image handling minimal: do not open every generated base or row in the parent rollout. Workers return only the selected source path and a one-sentence QA note; the parent records the selected source path in the manifest.
- `prepare_pet_run.py` also creates 9 row-specific layout guide images under `references/layout-guides/`, one per animation state. Row jobs attach the matching guide as a layout-only input so the model can follow the correct frame count, spacing, centering, and safe padding. Treat these guides as invisible construction references: the generated row strip must not include visible boxes, borders, center marks, labels, guide colors, or the guide background.
+ `prepare_pet_run.py` creates 9 row-specific layout guide images under `references/layout-guides/`, one per animation state. Row jobs attach the matching guide as a layout-only input so the model can follow the correct frame count, spacing, centering, and safe padding. Treat these guides as invisible construction references: the generated row strip must not include visible boxes, borders, center marks, labels, guide colors, or the guide background.
- When generating row strips, keep the identity lock in the row prompt authoritative: do not redesign the pet, and preserve the same head shape, face, markings, palette, prop, outline weight, body proportions, and silhouette. A row that looks like a related but different pet is failed even if the deterministic geometry QA passes.
+ When generating row strips, keep the identity lock in the row prompt authoritative. Preserve the same style, face, markings, palette, materials, prop design, body proportions, and silhouette from the canonical base. Row jobs attach the layout guide and canonical base by default; the decoded base is kept in the run folder for deterministic processing rather than sent as a redundant generation input.
- Generate and record `running-right` before deciding how to complete `running-left`. Inspect `running-right` against the base and references. If the pet is visually symmetric enough that a horizontal mirror preserves identity, prop placement, handedness, markings, lighting, text-free details, and direction semantics, derive `running-left` with:
+ If `$imagegen` returns a transport-level `Bad Request` for a row, retry that same row once with its generated `retry_prompt_file`. The retry prompt preserves the row id, frame count, chroma key, canonical-base identity, and state action. Keep the canonical base attached. If the retry still fails, stop and report the failing row and prompt paths instead of switching to any other generation path.
+ 4. After selecting a generated output for a job, copy it into the decoded output path and mark the job complete. For `base`, also create the canonical identity reference:
+
```bash
+ RUN_DIR=/absolute/path/to/run
+ JOB_ID=<job-id>
+ SOURCE=/absolute/path/to/generated-output.png
+ OUTPUT_REL=$(jq -r --arg id "$JOB_ID" '.jobs[] | select(.id == $id) | .output_path' "$RUN_DIR/imagegen-jobs.json")
+ mkdir -p "$(dirname "$RUN_DIR/$OUTPUT_REL")"
+ cp "$SOURCE" "$RUN_DIR/$OUTPUT_REL"
+ ```
+
+ ```bash
+ if [ "$JOB_ID" = "base" ]; then mkdir -p "$RUN_DIR/references"; cp "$RUN_DIR/$OUTPUT_REL" "$RUN_DIR/references/canonical-base.png"; fi
+ ```
+
+ ```bash
+ UPDATED_AT=$(date -u +%Y-%m-%dT%H:%M:%SZ)
+ TMP_MANIFEST=$(mktemp)
+ jq --arg id "$JOB_ID" --arg source "$SOURCE" --arg at "$UPDATED_AT" '(.jobs[] | select(.id == $id)) += {status: "complete", source_path: $source, completed_at: $at}' "$RUN_DIR/imagegen-jobs.json" > "$TMP_MANIFEST"
+ mv "$TMP_MANIFEST" "$RUN_DIR/imagegen-jobs.json"
+ ```
+
+ If the copied source is under `${CODEX_HOME:-$HOME/.codex}/generated_images`, delete the original generated file after the decoded copy exists:
+
+ ```bash
+ GENERATED_ROOT="${CODEX_HOME:-$HOME/.codex}/generated_images"
+ case "$SOURCE" in
+ "$GENERATED_ROOT"/*)
+ rm -f "$SOURCE"
+ rmdir "$(dirname "$SOURCE")" 2>/dev/null || true
+ ;;
+ esac
+ ```
+
+ 5. Derive `running-left` only when it is visually safe:
+
+ ```bash
python "$SKILL_DIR/scripts/derive_running_left_from_running_right.py" \
--run-dir /absolute/path/to/run \
--confirm-appropriate-mirror \
--decision-note "<why mirroring preserves this pet's identity>"
```
- If there is any asymmetric side-specific marking, readable text, non-mirrored logo, handed prop, one-sided accessory, lighting cue, or direction-specific pose that would become wrong when flipped, do not mirror. Generate `running-left` with `$imagegen` using its row prompt and all listed grounding images, including `decoded/running-right.png` as a gait reference.
+ That script mirrors each generated frame slot in place so the leftward row preserves the rightward row's temporal order. Do not replace it with a whole-strip mirror that reverses animation timing.
- For the built-in path, record the selected source image from `$CODEX_HOME/generated_images/.../ig_*.png`. Do not record files from the run directory, `tmp/`, hand-made fixtures, deterministic row folders, or post-processed copies as visual job sources.
+ 6. When all jobs are complete, run the image-processing scripts directly:
- 4. After selecting a generated output for a job, ingest it:
+ ```bash
+ RUN_DIR=/absolute/path/to/run
+ mkdir -p "$RUN_DIR/final" "$RUN_DIR/qa"
+ ```
```bash
- python "$SKILL_DIR/scripts/record_imagegen_result.py" \
- --run-dir /absolute/path/to/run \
- --job-id <job-id> \
- --source /absolute/path/to/generated-output.png
+ python "$SKILL_DIR/scripts/extract_strip_frames.py" \
+ --decoded-dir "$RUN_DIR/decoded" \
+ --output-dir "$RUN_DIR/frames" \
+ --states all \
+ --method auto
```
- This copies the image to the exact decoded path expected by the deterministic pipeline and records source metadata in `imagegen-jobs.json`.
+ ```bash
+ python "$SKILL_DIR/scripts/inspect_frames.py" \
+ --frames-root "$RUN_DIR/frames" \
+ --json-out "$RUN_DIR/qa/review.json" \
+ --require-components
+ ```
- 5. When all jobs are complete, finalize:
+ ```bash
+ python "$SKILL_DIR/scripts/compose_atlas.py" \
+ --frames-root "$RUN_DIR/frames" \
+ --output "$RUN_DIR/final/spritesheet.png" \
+ --webp-output "$RUN_DIR/final/spritesheet.webp"
+ ```
```bash
- python "$SKILL_DIR/scripts/finalize_pet_run.py" \
- --run-dir /absolute/path/to/run
+ python "$SKILL_DIR/scripts/validate_atlas.py" \
+ "$RUN_DIR/final/spritesheet.webp" \
+ --json-out "$RUN_DIR/final/validation.json"
```
- Expected output:
+ ```bash
+ python "$SKILL_DIR/scripts/make_contact_sheet.py" \
+ "$RUN_DIR/final/spritesheet.webp" \
+ --output "$RUN_DIR/qa/contact-sheet.png"
+ ```
+ ```bash
+ python "$SKILL_DIR/scripts/render_animation_previews.py" \
+ --frames-root "$RUN_DIR/frames" \
+ --output-dir "$RUN_DIR/qa/previews"
+ ```
+
+ If the preview GIFs show size popping or baseline jumps caused by per-frame fit-to-cell extraction, and the original row strip itself had stable scale and placement, rerun frame extraction with the explicit row-stability mode and then re-run inspection, atlas composition, validation, contact sheet generation, and previews:
+
+ ```bash
+ python "$SKILL_DIR/scripts/extract_strip_frames.py" \
+ --decoded-dir "$RUN_DIR/decoded" \
+ --output-dir "$RUN_DIR/frames" \
+ --states all \
+ --method stable-slots
+ ```
+
+ ```bash
+ python "$SKILL_DIR/scripts/inspect_frames.py" \
+ --frames-root "$RUN_DIR/frames" \
+ --json-out "$RUN_DIR/qa/review.json" \
+ --require-components \
+ --allow-stable-slots
+ ```
+
+ Use `stable-slots` as a deliberate QA-driven correction, not the default. It should reduce extraction-induced motion pops without hiding clipped wide poses or bad source strips.
+
+ Expected output before cleanup:
+
```text
run/
pet_request.json
imagegen-jobs.json
prompts/
decoded/
frames/frames-manifest.json
- final/spritesheet.png
final/spritesheet.webp
final/validation.json
qa/contact-sheet.png
+ qa/previews/*.gif
qa/review.json
qa/run-summary.json
- qa/videos/*.mp4
```
Package output is written outside the run directory by default. If `CODEX_HOME` is set, use it; otherwise use `$HOME/.codex`.
```text
${CODEX_HOME:-$HOME/.codex}/pets/<pet-name>/
pet.json
spritesheet.webp
```
- Review `qa/contact-sheet.png`, `qa/review.json`, `final/validation.json`, and `qa/videos/` before accepting the pet.
+ Package with shell and `jq`:
- Deterministic validation is necessary but not sufficient. Before calling the pet done, visually inspect the contact sheet for identity consistency. Block acceptance if any row changes species/body type, face, markings, palette, prop design, prop side unexpectedly, or overall silhouette.
+ ```bash
+ RUN_DIR=/absolute/path/to/run
+ PET_ID=$(jq -r '.pet_id' "$RUN_DIR/pet_request.json")
+ DISPLAY_NAME=$(jq -r '.display_name' "$RUN_DIR/pet_request.json")
+ DESCRIPTION=$(jq -r '.description' "$RUN_DIR/pet_request.json")
+ PET_DIR="${CODEX_HOME:-$HOME/.codex}/pets/$PET_ID"
+ mkdir -p "$PET_DIR"
+ cp "$RUN_DIR/final/spritesheet.webp" "$PET_DIR/spritesheet.webp"
+ jq -n --arg id "$PET_ID" --arg displayName "$DISPLAY_NAME" --arg description "$DESCRIPTION" '{id: $id, displayName: $displayName, description: $description, spritesheetPath: "spritesheet.webp"}' > "$PET_DIR/pet.json"
+ ```
- ## Subagent Row Generation
+ Write `qa/run-summary.json` after packaging:
- After the base job has been recorded and `references/canonical-base.png` exists, row-strip visual generation must use subagents unless the user explicitly says not to use subagents for this session. Before row generation, state that subagents are being used and which row jobs are being delegated. If subagents cannot be spawned because the current environment or tool policy blocks them, stop before row-strip generation, explain the blocker, and ask for explicit user direction before continuing sequentially.
+ ```bash
+ jq -n --arg run_dir "$RUN_DIR" --arg spritesheet "$RUN_DIR/final/spritesheet.webp" --arg validation "$RUN_DIR/final/validation.json" --arg contact_sheet "$RUN_DIR/qa/contact-sheet.png" --arg review "$RUN_DIR/qa/review.json" --arg package "$PET_DIR" '{ok: true, run_dir: $run_dir, spritesheet: $spritesheet, validation: $validation, contact_sheet: $contact_sheet, review: $review, package: $package}' > "$RUN_DIR/qa/run-summary.json"
+ ```
- The parent agent must own the manifest and package writes.
+ After deterministic image processing, inspect `qa/contact-sheet.png` and `qa/previews/*.gif` with a lightweight visual QA worker before accepting the pet. Deterministic validation is necessary but not sufficient. Block acceptance if any row changes species/body type, face, markings, palette, material, prop design, style, prop side unexpectedly, or overall silhouette. Motion previews must also reject unintended size popping, reversed or stagnant directional cadence, wrong facing direction, and idle loops that are technically different but visually inert.
- Default flow:
+ After model visual QA accepts the contact sheet, remove intermediate run artifacts:
- 1. Parent runs `prepare_pet_run.py`.
- 2. Parent generates and records `base`.
- 3. Parent runs `pet_job_status.py`.
- 4. Parent spawns subagents for `idle` and `running-right` first as identity and gait checks.
- 5. Parent records the selected `idle` and `running-right` results returned by subagents.
- 6. Parent decides whether `running-left` is safe to derive by mirror; if not, parent treats it as a normal grounded row job delegated to a subagent.
- 7. Parent spawns subagents for every remaining non-derived row image-generation job.
- 8. Each subagent receives the row prompt and every listed input image path, invokes `$imagegen`, and returns only the selected `$CODEX_HOME/generated_images/.../ig_*.png` source path.
- 9. Parent alone runs `record_imagegen_result.py`, `derive_running_left_from_running_right.py`, repair queueing, finalization, QA, and packaging.
+ Keep `pet_request.json`, `final/spritesheet.webp`, `final/validation.json`, `qa/contact-sheet.png`, `qa/previews/`, `qa/review.json`, and `qa/run-summary.json`. Remove generated prompt files, layout guides, decoded row strips, extracted frames, `final/spritesheet.png`, and the imagegen job manifest. Skip cleanup when the user wants debug artifacts or the run still needs repair.
- Subagent write boundary: do not let subagents edit `imagegen-jobs.json`, copy files into `decoded/`, run `record_imagegen_result.py`, run `derive_running_left_from_running_right.py`, run `finalize_pet_run.py`, or package the pet. This avoids manifest races and keeps provenance checks centralized.
+ ## Lightweight Visual Workers
- Subagent handoff contract:
+ Use lightweight subagents for image-heavy work by default. This bounds each `$imagegen` rollout to one selected image, keeps contact-sheet vision payloads out of the parent thread, and reduces cost while preserving the full 9-state app contract.
- - Give each subagent exactly one row job unless you are intentionally batching adjacent simple rows.
- - Include the row id, the absolute prompt file path, the full prompt text or an instruction to read that exact prompt file, and every input image path with its role label from `imagegen-jobs.json`.
- - Explicitly remind the subagent that the prompt's transparency and effects rules are mandatory: no detached effects, no wave marks for `waving`, no speed lines or dust for directional running rows, no literal foot-running for the non-directional `running` row, and only attached opaque sprite-like tears/smoke/stars when allowed by the state prompt.
- - Tell the subagent to inspect the generated candidate for frame count, identity consistency, clean flat chroma-key background, safe spacing, and forbidden detached effects before returning it.
- - Tell the subagent to return only the selected original `$CODEX_HOME/generated_images/.../ig_*.png` source path plus a one-sentence QA note. The parent decides whether to record or repair it.
+ ## Subagent Delegation
- Use this template for each subagent:
+ Unless explicitly forbidden by the user, use subagents for this run. If the user has not allowed the use of subagents, or the intent on subagent use is vague, then ask the user for permission to spawn subagents for parallel lanes of work.
+ Parent responsibilities:
+
+ - run the brand discovery worker before preparation when the user provides a bare brand/product/company/prospect name
+ - prepare the run and inspect `imagegen-jobs.json`
+ - assign the base job, row jobs, and final contact-sheet QA to lightweight workers
+ - copy selected worker outputs into their decoded paths and mark jobs complete in `imagegen-jobs.json`
+ - create `references/canonical-base.png` from the selected base output
+ - run the approved `running-left` mirror derivation when appropriate
+ - run deterministic image processing, packaging, repair regeneration, and cleanup
+
+ Base worker responsibilities:
+
+ - handle only the `base` job
+ - read `prompts/base-pet.md` and use any listed reference images
+ - use `$imagegen` only
+ - honor any compact brand inspiration line in the prompt as broad visual/personality guidance, without copying logos, readable marks, UI screenshots, slogans, or text
+ - return only `selected_source=/absolute/path/to/selected-output.png` and `qa_note=<one sentence>`
+
+ Row worker responsibilities:
+
+ - handle exactly one row job
+ - read the row prompt and use all listed input images
+ - use `$imagegen` only; do not draw, edit, tile, or synthesize sprites locally
+ - perform a quick visual sanity check for frame count, identity, chroma background, spacing, clipping, and detached effects
+ - enforce the row prompt's transparency and effects rules, including no detached effects, no wave marks for `waving`, no speed lines or dust for directional running rows, no literal foot-running for the non-directional `running` row, and only attached opaque sprite-like tears/smoke/stars when allowed by the state prompt
+ - return only `selected_source=/absolute/path/to/selected-output.png` and `qa_note=<one sentence>`
+
+ Final visual QA worker responsibilities:
+
+ - inspect `qa/contact-sheet.png` plus the row GIFs under `qa/previews/`, with `qa/review.json` and `final/validation.json` as text context when useful
+ - verify all 9 rows match the Codex app state contract and the same pet identity
+ - return a compact result: `visual_qa=pass` or `visual_qa=fail`, plus row-specific repair notes when failing
+ - do not edit files, queue repairs, package, or clean up
+
+ Model choice for workers:
+
+ - Prefer a smaller capable model for brand discovery, since it returns a compact research brief rather than doing orchestration.
+ - Prefer a smaller capable model for visual workers, such as `gpt-5.4-mini` with medium reasoning, when model override is available.
+ - Use the parent/default model only for orchestration or when a smaller worker model is unavailable.
+ - Keep at most two generation workers active at once unless the user explicitly asks for higher parallelism. Run final visual QA as a single worker after deterministic image processing. Close workers after their result has been consumed.
+
+ Use this base worker prompt:
+
```text
- Generate the `<row-id>` row for this hatch-pet run.
+ Generate the hatch-pet base image.
Run dir: <absolute run dir>
- Prompt file: <absolute prompt file>
+ Job id: base
+ Prompt file: <absolute base prompt file>
Input images:
- <absolute path> — <role>
- - <absolute path> — <role>
- Read and follow the row prompt exactly, including the Transparency and artifact rules. Use `$imagegen` only; do not use local scripts to draw, tile, edit, or synthesize sprites.
+ Use $imagegen only. Read the base prompt and attach every listed input image. If the prompt contains brand inspiration, use it only as broad mascot-safe guidance; do not copy logos, readable marks, UI screenshots, slogans, or text. Before returning, visually check that the result is one centered full-body pet on a flat chroma background, with no text, scenery, shadows, or detached effects.
- Before returning, visually check:
- - exact requested frame count
- - same pet identity as the canonical base
- - clean flat chroma-key background
- - complete, separated, unclipped poses
- - no forbidden detached effects or slot-crossing artifacts
+ Do not edit manifests, copy into decoded, mark jobs complete, generate rows, run image-processing scripts, repair, package, or open unrelated files.
+ Do not include Markdown image previews, base64, or extra attachments in the final response.
- Do not edit manifests, copy into decoded, record results, mirror rows, finalize, repair, or package. Return only:
- selected_source=/absolute/path/to/$CODEX_HOME/generated_images/.../ig_*.png
+ Return exactly:
+ selected_source=/absolute/path/to/selected-output.png
qa_note=<one sentence>
```
- No silent sequential fallback: if subagents cannot be used for row-strip visual generation, stop and ask for explicit user direction before continuing without them. Only an explicit user instruction such as "do not use subagents" or "run this sequentially" authorizes a normal sequential row-generation path. The final answer must report which row jobs were delegated to subagents and which, if any, were mirrored or repaired by the parent.
+ Use this row worker prompt:
- ## Repair Workflow
+ ```text
+ Generate one hatch-pet row.
- If finalization stops because row QA failed, queue targeted repair jobs:
+ Run dir: <absolute run dir>
+ Row id: <row-id>
+ Prompt file: <absolute prompt file>
+ Retry prompt file: <absolute retry prompt file>
+ Input images:
+ - <absolute path> — <role>
+ - <absolute path> — <role>
- ```bash
- python "$SKILL_DIR/scripts/queue_pet_repairs.py" \
- --run-dir /absolute/path/to/run
+ Use $imagegen only. Read the row prompt and attach every listed input image. If imagegen returns Bad Request, retry once with the retry prompt and the same input images.
+
+ Before returning, visually check: exact frame count, same pet identity as canonical base, flat chroma background, complete separated unclipped poses, and no detached effects or guide marks. The prompt's transparency and effects rules are mandatory: no detached effects, no wave marks for `waving`, no speed lines or dust for directional running rows, no literal foot-running for the non-directional `running` row, and only attached opaque sprite-like tears/smoke/stars when allowed by the state prompt.
+
+ Do not edit manifests, copy into decoded, mark jobs complete, mirror rows, run image-processing scripts, repair, package, or open unrelated files.
+ Do not include Markdown image previews, base64, or extra attachments in the final response.
+
+ Return exactly:
+ selected_source=/absolute/path/to/selected-output.png
+ qa_note=<one sentence>
```
- Then repeat the `$imagegen` generation and `record_imagegen_result.py` ingest loop for each reopened row job. Regenerate the smallest failing scope: the failed row, not the whole sheet.
+ Use this final visual QA worker prompt:
- For identity repairs, use the canonical base image, original references, contact sheet, and exact row failure note as grounding context. Repair only the failed row while preserving the canonical pet identity.
+ ```text
+ Visually QA one finalized hatch-pet contact sheet.
- ## Secondary Image Generation Fallback
+ Run dir: <absolute run dir>
+ Contact sheet: <absolute run dir>/qa/contact-sheet.png
+ Preview dir: <absolute run dir>/qa/previews
+ Review JSON: <absolute run dir>/qa/review.json
+ Validation JSON: <absolute run dir>/final/validation.json
- `scripts/generate_pet_images.py` is a secondary fallback for this skill.
+ Inspect the contact sheet and the preview GIFs visually. Confirm the same pet identity, style, palette, silhouette, face, proportions, and props across all rows:
+ 0 idle, 1 running-right, 2 running-left, 3 waving, 4 jumping, 5 failed, 6 waiting, 7 running, 8 review.
- Use it only when the installed `$imagegen` system skill is unavailable or cannot be invoked in the current environment. Normal pet creation should delegate visual generation to `$imagegen`, because `$imagegen` owns the built-in-first image generation policy and its own CLI fallback behavior.
+ Fail rows with identity drift, missing/blank frames, copied guide marks, white/nontransparent backgrounds, cropped bodies, slot overlap, detached effects, shadows/glows/smears/dust, chroma-key artifacts, motion that does not match the row state, unintended size popping, wrong facing direction, reversed or non-alternating gait, or idle loops that are effectively static.
- Run the secondary fallback only after explaining why `$imagegen` cannot be used:
+ Do not edit files, queue repairs, package, clean up, or inspect unrelated files.
- ```bash
- python "$SKILL_DIR/scripts/generate_pet_images.py" \
- --run-dir /absolute/path/to/run \
- --model gpt-image-2 \
- --states all
+ Return exactly:
+ visual_qa=pass|fail
+ qa_note=<one sentence summary>
+ repair_rows=<comma-separated row ids, or none>
+ repair_notes=<short row-specific notes, or none>
```
- The secondary fallback requires `OPENAI_API_KEY`.
+ ## Repair Workflow
+ If frame inspection or final visual QA fails, read `qa/review.json`, regenerate the smallest failing scope, copy the replacement row into the same decoded output path, and keep that job marked complete with the new `source_path` and `completed_at`. Repair the failed row, not the whole sheet.
+
+ For identity repairs, use the canonical base image, original references, contact sheet, and exact row failure note as grounding context. Give the row worker the existing row prompt plus a compact repair note from `qa/review.json`; preserve the canonical pet identity and chosen style.
+
+ For extraction-induced motion popping, do not regenerate imagery first. If the source strip already preserves row-level scale and baseline, rerun the deterministic pipeline with `--method stable-slots`, inspect with `--allow-stable-slots`, then re-check the preview GIFs. Regenerate the row only when the original strip itself is clipped, unstable, or semantically wrong.
+
## Rules
- Keep `$imagegen` as the primary generation layer.
+ - For brand/product/company/prospect requests without a concrete avatar description or reference image, run brand discovery before base generation and pass only the compact brief into the run.
+ - Use `$imagegen` as the only visual generation layer. Do not invoke image APIs, image CLIs, local raster generators, or one-off generation scripts from this skill.
- Keep reference images attached/visible for `$imagegen` whenever the chosen path supports references.
- Attach the row's `references/layout-guides/<state>.png` image to every row-strip job as a layout-only guide, and do not accept outputs that copy guide pixels.
- - Use subagents for row-strip visual generation after the parent records the base image. The parent may generate the base, but row-strip jobs belong to subagents unless the user explicitly says not to use subagents for this session.
+ - Use lightweight visual workers for base generation, row-strip visual generation, and final contact-sheet QA by default; the parent owns manifest updates, deterministic image scripts, packaging, and cleanup.
- Generate every normal visual job with `$imagegen`: base plus all row strips that are not explicitly approved `running-left` mirror derivations.
- Treat only the base job as eligible for prompt-only generation; every row job must attach its listed grounding images.
- - Delegate `running-right` first, then mirror `running-left` only when visual inspection confirms a mirror preserves identity and semantics; otherwise delegate `running-left` as a normal grounded `$imagegen` row.
+ - Generate `running-right` before deciding whether `running-left` can be mirrored.
+ - When `running-left` is mirrored, preserve frame order and timing semantics; derive it through the deterministic script instead of mirroring an entire strip wholesale.
+ - Do not derive or reuse `waiting`, `running`, `failed`, `review`, `jumping`, or `waving` from another state; each has distinct app semantics and must be generated as its own row.
- Never substitute locally drawn, tiled, transformed, or code-generated row strips for missing `$imagegen` outputs.
- - Never manually mutate `imagegen-jobs.json` to claim a visual job completed.
- - Do not rely on generated images for exact atlas geometry; use this skill's deterministic scripts.
+ - Only mark a visual job complete after its selected output has been copied into the decoded output path.
+ - Do not rely on generated images for exact atlas geometry; use this skill's deterministic image scripts.
- Use the chroma key stored in `pet_request.json`; do not force a fixed green screen.
- - Keep the pet's silhouette, face, materials, palette, and props consistent across all rows.
- - Enforce the transparency and effects rules above in every base, row, and repair prompt.
- - Treat visual identity drift as a blocker even when `qa/review.json` and `final/validation.json` have no errors.
+ - Keep the pet's silhouette, face, materials, palette, style, and props consistent across all rows.
+ - Treat visual identity or style drift as a blocker even when `qa/review.json` and `final/validation.json` have no errors.
- Treat a contact sheet that shows cropped references, repeated tiles, white cell backgrounds, or non-sprite fragments as failed.
+ - Treat preview GIFs that show extraction-induced size popping, reversed directional timing, wrong facing direction, or inert idle loops as failed.
- Treat forbidden detached effects, chroma-key-adjacent artifacts, shadows, glows, smears, dust, landing marks, wave marks, speed lines, or motion trails as failed rows.
- Treat `qa/review.json` errors as blockers. Warnings require visual review.
## Acceptance Criteria
- Final atlas is PNG or WebP, `1536x1872`, transparent-capable, and based on `192x208` cells.
- Used cells are non-empty and unused cells are fully transparent.
- Atlas follows the row/frame counts in `references/animation-rows.md`.
- - Contact sheet and preview videos have been produced unless explicitly skipped.
+ - Contact sheet and per-row motion previews have been produced and inspected by a lightweight visual QA worker.
- `qa/review.json` has no errors.
- Row-by-row review confirms the animation cycles are complete enough for the Codex app.
+ - Motion previews do not show unintended size popping, reversed directional cadence, or wrong row semantics.
+ - Non-pixel styles are accepted when readable at pet size and consistent across rows.
- `${CODEX_HOME:-$HOME/.codex}/pets/<pet-name>/pet.json` and `${CODEX_HOME:-$HOME/.codex}/pets/<pet-name>/spritesheet.webp` are staged together for custom pets.