Artist Self Evolve

# Art Pack — <game-slug>

## <Group>                          # Background, Player, Boss, FX, UI, Map, Audio, ...

### <raw-asset>                     # name of the raw image, NOT a final manifest key
- prompt                            # verbatim from .vibegame/logs/imagegen.jsonl

Rules:

- If a prompt cannot be recovered (even via fallback), replace the whole `prompt` bullet with a single line `- prompt missing — see <pointer>`, where `<pointer>` is `spec/art/<file>.md § <X>` or `spec/contracts/<file>.md Pattern <N> <slug>` — whichever document owns the generation rules for this raw class.
- The **Hints** section is omitted when existing `spec/art/*` docs already cover the raw. Hints are deltas, not restatements. When the raw is cut into multiple finals, the Hints should point at the contract that owns the cut workflow (the cut itself lives in the contract's `#### Artist` chapter, not here).
- Per-project specifics (image resolution, runtime path, manifest key) are project variables and do **not** belong in art-pack.

This inventory is the **empirical** raw-asset list for the sub-genre — the prompts a real project of this kind ran to produce the manifest, not what the design ideal called for.

### Phase 2: Fill `#### Artist` chapters when the lead requests

The lead drafts new or revised contracts during `self-evolve` Step 5. For each contract whose asset class touches your domain, the lead sends a message asking you to fill that contract's `#### Artist` chapter. Process one contract per message.

The chapter answers exactly three questions, packaged as one Workflow:

1. **Generate** — what assets does this pattern need, and how does artist produce them.
2. **Package** — how does artist turn raw output into shippable final assets, manifest entries, and node templates.
3. **Verify** — what does artist check before handing off.

Canonical references: [`status_bar.md`](../../.vibegame/spec/contracts/status_bar.md) (3-asset composite, bbox verification loop) and [`charge-family.md`](../../.vibegame/spec/contracts/charge-family.md) (3-sheet decomposition, character-scale alignment). Use these as structural templates; do not invent alternative layouts.

#### Body shape

```markdown
#### Artist

<one-line lead: what scope of work artist owns for this pattern. Example:
"Artist owns three independent sprite sheets covering build / peak / release.">

##### Workflow

1. **Generate**

   <asset breakdown — list every raw image this pattern needs and what each
    contains. Point each at its matching `### <raw-asset>` heading in
    `skeletons/<slug>/art-pack.md`. Inline a project-neutral templated prompt
    per raw image. Add any non-obvious generation rules (style anchor, marker
    color, loop closure, character-scale anchor, ...).>

2. **Package**

   <cut + chroma-key + concat + scale alignment, inlined as concrete CLI
    invocations (`vibegame art rmbg`, `cut`, `concat`). End with final asset
    paths under `assets/...`, manifest entries (with `landmark` if any), and
    the `.node.json` shape consumed by the module.>

3. **Verify**

   <`vibegame art label` overlay + `vibegame vlm` PASS/FAIL prompt, iterated
    until PASS. Cover every check artist must clear before delivery: bbox
    alignment on slot, character-scale consistency across sheets, no marker
    halo, loop seam invisible, etc.>

Common mistakes:

- <anti-patterns specific to this asset class — packing 3 sheets into one,
  baking dynamic text into art, delivering hollow slot, marker-colored
  background instead of transparent, ...>