Add asset creation skill and artist agent for Stickman Studio

- Introduced a new artist agent to create and review vector, raster, clothing, prop, and animation assets based on user prompts or reference images. - Created an asset-creation skill to manage the delegation, review, approval, and handoff processes for graphical assets and animations. - Added project format routing documentation to guide asset creation and ensure consistency in Stickman Studio. - Established a review workflow for asset promotion, ensuring thorough validation and user approval before finalizing assets. - Documented the specifications for scenery, backgrounds, and vector surface finishes to enhance the child experience in the Sandbox Stage.
2026-10-15 14:35:44 -04:00
parent f852a4d6de
commit 36032ebb1e
10 changed files with 389 additions and 7 deletions
@@ -0,0 +1,36 @@
+# Asset review and promotion
+
+## Review bundle
+
+Use `content/review/artist/<request-slug>/`, where the slug is short, lowercase, and hyphenated. This tree is ignored by Git and is not scanned by the immediate-child prop and stickman library scanners.
+
+Keep:
+
+- versioned candidate files such as `briefcase-v1.prop` or `detective-coat-v2.stk`;
+- `preview.png` or a clearly named contact sheet;
+- animation key-pose captures when applicable;
+- `review.md`.
+
+`review.md` records:
+
+- the requested outcome and intended use;
+- which supplied images were references and which, if any, were edit targets;
+- creative choices and optional Artist suggestions;
+- external reference URLs and known license/usage notes;
+- candidate filenames and intended production destinations;
+- validation commands or scenes, observed results, and unverified outcomes.
+
+Do not copy browsed reference images into the bundle unless the user owns them or their license permits redistribution.
+
+## Approval boundary
+
+Show the preview and report the candidate paths. Wait for explicit approval before copying a candidate to a production location. Revision requests produce a new version rather than destroying the earlier candidate.
+
+After approval:
+
+- `.prop` -> `content/props/`
+- `.stk` -> `content/stickmen/`
+- PNG -> the relevant existing `resources/` category, or `resources/art/<kind>/` when necessary
+- animation -> the approved specification's rig/tool asset location
+
+Never overwrite an existing production file unless the user specifically approves replacement. Do not delete the review bundle unless the user asks for cleanup.