Map Systems

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 "Map Systems" for me. It decomposes a game concept into individual systems. It reads design/gdd/game-concept.md (or design/game-brief.md at the minimal workflow tier, and fails with a clear message if neither exists), enumerates explicit and inferred implicit systems with the user, maps their dependencies into layers (Foundation, Core, Feature, Presentation, Polish), flags circular dependencies and bottleneck systems, assigns priority tiers (MVP, Vertical Slice, Alpha, Full Vision), and writes the systems index to design/gdd/systems-index.md from the template at .claude/docs/templates/systems-index.md, then updates production/session-state/active.md. In full review mode it spawns the template's technical-director (gate TD-SYSTEM-BOUNDARY), producer (PR-SCOPE) and creative-director (CD-SYSTEMS) agents. Its "next" mode, or naming a system, hands off to the separate /design-system skill. Its allowed tools include Edit and the TaskCreate/TaskGet/TaskList/TaskUpdate task tools. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/map-systems/ folder at the pinned commit: 1 file 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/map-systems/ 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 d27959d0043bd8c9f08c0f3fb56aa66de8e6ce84812a7e43d5f2d2c43cae01dd 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: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. - 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 file: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys review_mode, automation, workflow, docs.density, project.stage), reads the concept, pillars and any existing systems index under design/gdd/, the director-gate documents under .claude/docs/director-gates/ and the systems-index template, spawns the template's technical-director, producer and creative-director agents in full review mode, and hands individual system design off to the separate /design-system skill — files, agents and a skill that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. - At use time it writes the systems index to design/gdd/systems-index.md and updates production/session-state/active.md. In collaborative mode, and for a new index in guided mode, it asks "May I write…?" first; one disclosed exception: in guided mode, updating an index that already exists is written without waiting for an explicit yes, after presenting the summary and naming the destination, and is reported afterwards. It also uses the task tools (TaskCreate and friends). No account, key or payment is named in the file. - Do not map any system, do not run any template hook or 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. 3. When I say "yes, install", install it as a skill: copy the whole map-systems folder into the agent's skills directory, in a folder named exactly "map-systems", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: map-systems), the 1 file 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 (it resolves its settings through the template's yaml-helper hook, reads the template's docs and templates, uses its director agents in full review mode and hands off to /design-system), and that in guided mode an update to an existing systems index is written without a separate explicit yes, as disclosed above). 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.