artist-self-evolve

# Artist Self-Evolve Learn, from a completed project, the prompt patterns and art rules that reliably produced its assets. The lessons are stored in two places: - `skeletons/<slug>/art-pack.md` — the sub-genre's empirical raw-asset inventory (prompt + layout + Hints per raw image). Direct write, full responsibility. - `spec/contracts/<x>.md` `#### Artist` chapters — per-pattern asset workflows. You fill the chapter when lead drafts a new or revised contract. ## Input The lead's dispatch message provides: - `game-slug` — the project's sub-genre slug. All per-project outputs land under `skeletons/<game-slug>/`. If `game-slug` is missing from the dispatch message, reply to the lead asking for it. Do not guess from `.vibegame/GDD.md` or `project.json` — the slug is the lead's decision, not yours. ## Workflow ### Phase 0: Find actually-used assets Scan, in this order: - `assets/manifest.json` — every registered asset. - `.vibegame/assets.md` — asset notes and status. - `.vibegame/GDD.md` — what the design called for. - The game's runtime code — which manifest keys actually load at runtime. The output of this phase is the **empirical final-asset list** — the manifest keys actually loaded at runtime, minus anything unused / replaced / stale. This list is internal to your run; you do not write it to a file. Use it as Phase 1's input. ### Phase 1: Trace each final asset back to its raw image; recover prompts; write `art-pack.md` A final asset rarely equals one raw `vibega...