Settings

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 "Settings" for me. The skill itself views or changes the studio template's project configuration: with no argument it prints every effective setting of project.yaml merged with project.local.yaml (with each value's source, local-override and locked annotations), with a key it prints that one setting, and with key=value it writes project.yaml (team-wide) — or project.local.yaml (per-developer, gitignored) with the --local form. Every write passes an approval gate (AskUserQuestion) — the file states config writes to project.yaml are a schema_changes decision that is confirmed even in autonomous mode — plus enum validation, a known-key check, and warnings when the key is RESERVED (stored, but no skill or hook reads it, so setting it changes no behaviour — it warns, it never refuses) or shadowed by a local override; project-wide locked keys cannot be set locally. To do this it runs the template's hooks/yaml-helper.sh functions (resolve_setting, get_yaml_key, validate_yaml_enum, validate_enum_value, is_locally_overridable) and the template script .claude/scripts/config-set.sh in dry-run mode, and greps .claude/docs/effects-map.md for the reserved set — all template files outside this skill's folder. Writes are made with Edit or Write on the YAML files themselves; no external YAML library is used. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/settings/ 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/settings/ 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 5741b2ef90d60ee3ee350b908d106c10fcd037ad280d2a9ee4cb8f8a7fcc506e 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. The helper script and the config-set script it calls at use time are NOT in this folder — they belong to the template. - 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 audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh functions and the template script .claude/scripts/config-set.sh (dry-run), greps .claude/docs/effects-map.md, reads .claude/docs/settings-guidance.md for advice, and reads or edits my project's project.yaml and project.local.yaml at the project root — helpers, docs and config files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own (if yaml-helper.sh is missing, it reports this is not a CCGS project and exits). - At use time the view modes write nothing. The set modes edit exactly one configuration file — project.yaml (team-wide) or project.local.yaml (my gitignored local override) — and only after the AskUserQuestion approval gate, which applies even in autonomous mode for project.yaml writes. No third-party service, account or credential is named in the file, and no network call is made. - Do not view or change any setting, do not run any template helper or script, 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 settings folder into the agent's skills directory, in a folder named exactly "settings", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: settings), 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 (its yaml-helper functions, config-set script and effects-map live in the template, outside this folder), and that at use time its writes to project.yaml or project.local.yaml always pass an approval gate). 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.