← ClaudeAtlas

art-asset-registrylisted

Track generated 2D/3D assets in one ledger: which prompt made each file, approvals, what's stale.
tipoLi5890/unity-dev-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# art-asset-registry — what exists, where it came from, who approved it Every generation skill writes files, and none of them remembers which prompt, anchor, seed or workflow made which file, or whether anyone looked at it. A hand-written `manifest.md` drifts the same way in every project: rows for files that are gone, files no row names, rows still `PENDING` long after the spec locked, and nothing that notices an approved image being overwritten. The ledger keeps the facts a script can know (paths, hashes, lineage, links, gates, status) and leaves the prose to people. It treats 2D and 3D alike: a sprite sheet, a mesh with its raw original, a rig with the `.blend` it came from, a clip, a QA sheet a decision rests on. ## Start here — the request, and where it is answered | The request or symptom | Read | |---|---| | "Track generated assets": starting a ledger, recording after each generation (sha256 per file, each `.blend` version too), `check` and its fixes, moving a file, several writers at once | `reference/workflow.md`; [Commands](#commands) | | "Which asset came from which prompt": lineage (parent, links to the art direction, a job or an evidence image), what a field means, the vocabularies, how an id is made, every check rule, the exit codes (0/2/3), the JSON output | `reference/ledger-schema.md` | | "Which version is current", or setting a status as a person's act | [Working contract](#working-contract); `history ID`, `status ID approved` in `reference/workflow.md` |