nexu-io/open-design / skills/hatch-pet
hatch-pet
VerifiedCreate, repair, validate, preview, and package Codex-compatible animated 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.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 10.5 KB |
| README.md | markdown | 2.6 KB |
| SKILL.md | skill md | 23.3 KB |
| agents/openai.yaml | config | 560 B |
| references/animation-rows.md | markdown | 1.4 KB |
| references/codex-pet-contract.md | markdown | 788 B |
| references/qa-rubric.md | markdown | 3.2 KB |
| scripts/compose_atlas.py | script | 5.1 KB |
| scripts/derive_running_left_from_running_right.py | script | 4.8 KB |
| scripts/extract_strip_frames.py | script | 10.4 KB |
| scripts/finalize_pet_run.py | script | 13.7 KB |
| scripts/generate_pet_images.py | script | 10.2 KB |
| scripts/inspect_frames.py | script | 8.3 KB |
| scripts/make_contact_sheet.py | script | 2.9 KB |
| scripts/package_custom_pet.py | script | 3.4 KB |
| scripts/pet_job_status.py | script | 4.0 KB |
| scripts/prepare_pet_run.py | script | 26.8 KB |
| scripts/queue_pet_repairs.py | script | 6.6 KB |
| scripts/record_imagegen_result.py | script | 7.7 KB |
| scripts/render_animation_videos.py | script | 4.1 KB |
| scripts/render_animation_videos.sh | script | 152 B |
| scripts/test_generate_pet_images.py | script | 5.0 KB |
| scripts/validate_atlas.py | script | 4.7 KB |
README.md
View on GitHub# hatch-pet (vendored)
This directory is a **vendored copy** of the Codex `hatch-pet` skill. It is
checked into the OpenDesign repo (rather than pulled in as a Git submodule
or an npm package) so that:
- Any OpenDesign agent can run the skill end-to-end without a network
fetch, an extra install step, or an out-of-tree clone.
- The packaged desktop build can ship the skill as inert static assets
alongside the rest of `skills/`.
- Reviews of changes that touch pet generation can see the skill source in
the same diff as the daemon / web wiring that consumes it.
The vendoring trade-off is: this copy will not auto-track upstream
revisions. If the upstream skill changes (atlas geometry, manifest shape,
script CLIs), this copy must be re-synced by hand. Treat it as a frozen
snapshot, not a live dependency.
## Provenance
- Skill: `hatch-pet`
- Pinned upstream reference (declared in `SKILL.md` frontmatter): see the
`upstream:` field — at vendoring time this pointed to the Codex curated
`skills/.curated/hatch-pet` tree. That URL was not publicly resolvable
at the time this README was written; treat the vendored snapshot in this
directory as the authoritative source-of-truth for OpenDesign and
re-confirm the upstream pointer the next time a re-sync is performed.
- License: Apache License 2.0 (`LICENSE.txt` next to this README). The
copyright line in the bundled `LICENSE.txt` is left unfilled because no
separate copyright holder was identified at vendoring time. If a future
re-sync confirms the upstream copyright holder, populate the standard
Apache `Copyright [yyyy] [name of copyright owner]` line and add a
`NOTICE` file mirroring upstream attribution.
## Re-syncing this skill
When the upstream skill changes:
1. Locate the upstream source (Codex `skills/.curated/hatch-pet` or the
superseding location).
2. Replace the contents of this directory with the upstream snapshot,
preserving only this `README.md` and any Open-Design-specific notes
inside `SKILL.md`'s `> **OpenDesign integration.**` blockquote.
3. Update the `upstream:` field in `SKILL.md` frontmatter with the exact
commit SHA / tag of the snapshot.
4. Update `LICENSE.txt` and add a `NOTICE` file if upstream now ships
attribution metadata.
## Where outputs land
The skill packages each pet under
`${CODEX_HOME:-$HOME/.codex}/pets/<pet-id>/` with `pet.json` and
`spritesheet.{webp,png,gif}`. The daemon scans that directory in
`apps/daemon/src/codex-pets.ts`; the web pet settings list and one-click
adopt pets from there. See `docs/codex-pets.md` for the end-user setup
flow (including how OpenDesign behaves when Codex is not installed).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |