Codex pet generator prompt
Pick the kind, style, mood, and details you want, then copy one Codex pet prompt into Codex. The builder follows the installed hatch-pet skill instead of freezing one atlas version, asks for package-ready output, and requires deterministic plus visual QA. If you prefer an existing pet, use the finished package path first in Codex pet gallery or the install guide.
Use this for new pets
If you already have a package you can install, the fastest route is gallery to install. Use this Codex pet generator path for new ideas that do not match any current pet and for style changes you want to prototype before committing a new file layout.
Get immediate results from catalog pets with package zip, manifest, and spritesheet already prepared.
Verify firstPreview generated outputValidate the generated skill version, reported atlas states, and motion behavior before copying files into ~/.codex/pets.
Install pathFinish with local setupFollow the install checklist once the generated prompt is ready.
Prompt builder
This does not generate images in the browser. It gives Codex a complete brief that asks the AI to check the skill, run hatch-pet, and verify the final package.
You only need to copy the brief. It tells the AI to check whether hatch-pet is available, then either run the workflow or stop and explain the missing setup.
One click creates one measured copy action.
How to use
Select a kind, current hatch-pet style, mood, and motion profile that match the Codex pet you want to hatch.
Describe the subject, silhouette, colors, accessories, behavior, and any reference or brand cues in concrete language.
Paste the generated brief into Codex. The brief asks the AI to check hatch-pet first, so you do not need to manually verify the skill before copying.
After the AI reports a finished package, review its contact sheet, motion previews, manifest version, and atlas dimensions before using /pet.
Prompt FAQ
No. The generated brief includes an AI preflight step. It tells the AI to check whether hatch-pet is available, then either run the pet generation workflow or stop and explain the missing setup.
A good hatch-pet prompt should name the subject, kind, visual style, mood, reference or brand cues, and key readable details. It should tell the AI to verify hatch-pet, follow that installed skill's current atlas and manifest contract, run deterministic checks, inspect contact sheets and motion previews, and report the packaged files and validation result.
No. hatch-pet has to be installed and discoverable as a Codex skill first. If the skill is missing, the AI should stop and explain how to install it instead of trying to invent a spritesheet.
No. Describe the character and the important behavior states, then let the generation workflow produce the frame set. Over-specifying every frame can make the prompt brittle and less visually consistent.
Do not assume that. Existing packages on this site use the documented 8 by 9 catalog contract, while an installed hatch-pet skill may introduce a newer manifest or atlas version. Ask the workflow to follow its current contract and report the resulting version, dimensions, rows, and frame cells.
You should avoid publishing pets that depend on protected characters, logos, or brand assets unless you have the rights. Safer prompts describe an original companion with its own silhouette, colors, and personality.