avatar-forge-skill: Instructions file for Codex

AvatarForge development agreements

Use this file as the repository-level operating guide for agents and contributors. Keep user-facing generation behavior in SKILL.md and references/; keep development process, repository layout, and acceptance gates here.

Working agreements

• Preserve the avatar-forge-skill skill name, stable Pack IDs, and the 14-field Style Contract.
• Prefer pnpm when installing development dependencies.
• Ask for confirmation before adding any production dependency.
• Run npm test after modifying JavaScript files. If the repository has no package.json, report that the test was not applicable rather than inventing a command.
• Use apply_patch for text edits. Preserve unrelated user changes and do not commit, publish, package, or install the Skill unless requested.

Current operating model

Request-routing modes

Resolve requests in this precedence order:

1. explicit current user instruction;
2. explicitly invoked locked or saved style;
3. explicit medium;
4. named character default style;
5. scene preset default.

Route the request through one of these entry modes:

• Direct description: infer the scene and Pack and proceed when optional details can be absorbed by defaults.
• Scene first: use references/scene-presets.md; scene presets choose content and a complete Pack but never replace Pack fields with loose prose.
• Explicit medium: select the full matching Pack even when the scene has another default.
• Named character: load identity anchors and only references eligible for the active Pack.
• Locked or named style: restore the exact stored contract and fingerprint; fork rather than silently weakening a locked field.
• Series/gallery/team: use references/series-batches.md and separate immutable structure, content slots, and adaptive style slots.
• Reference image: separate identity evidence from incidental crop, clothing, lighting, background, and medium.

Batch modes

Choose exactly one batch mode before materializing prompts: