Asset Spec

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Asset Spec" for me. It is the Game Studios workflow that turns design documents into per-asset visual specs: given a system, level or character argument (or, with no argument, the next unspecced item from design/assets/entity-inventory.md or the asset manifest — building that entity and screen inventory from the systems index, GDD visual/audio sections, the entity registry and the art bible first when none exists), it writes a spec for each asset plus an AI generation prompt for it, consistent with design/art/art-bible.md — it runs after the art bible. The skill states its own external-action guard: invoking an external image generator always prompts regardless of automation mode; today the skill only emits the generation-prompt text and no live generation is wired in. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/asset-spec/ folder at the pinned commit: 1 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/asset-spec/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 8e9126653dcf25bdd2e197ee9df6587e3ffd7ee67de7103087cf8971c59fe025 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (20386 characters of instructions in a single file; there are no companion files in its folder). Nothing in the folder is run during installation; companion files are instructions/references the skill reads at use time, copied as-is. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh, reads the template's .claude/docs/ mode documents, and may spawn template agents or call template scripts under .claude/scripts/ — files and agents that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. Inside the template it works on my project's own files, locally. - No account, key, payment or third-party service is named in the files I read; any file it writes at use time is in my own project and follows the template's ask-before-writing collaborative conventions described in the skill. - Do not run any template hook or script, do not spawn any template agent, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. - One external-action point is stated in the skill itself: today it only emits AI generation-prompt text, but actually invoking an external image generator would always prompt first, regardless of automation mode, because that is an irreversible external action. 3. When I say "yes, install", install it as a skill: copy the whole asset-spec folder into the agent's skills directory, in a folder named exactly "asset-spec", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: asset-spec), the 1 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (its inputs are the template project's GDDs, registry and art bible), that it writes per-asset spec files with AI generation prompts in my project, and that it never calls an external image generator without asking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.