Quick Design

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 "Quick Design" for me. The skill itself is the lightweight design path for changes under about one week of implementation — tuning adjustments, minor behavioural tweaks, small additions to an existing system, or a small standalone system — that skip a full GDD: it classifies the change (Tuning, Tweak, Addition or New Small System, confirmed with the user via AskUserQuestion), scans the relevant GDD, the systems index, prior quick specs and data files, drafts a spec in the format for that category, presents it in full, and writes it to design/quick-specs/[name]-[date].md only after approval and a second explicit ask; a required GDD update is asked separately, showing the exact old-versus-new text, and is never made without explicit approval. A change that is too large is stopped and redirected to /design-system. It resolves the studio configuration (automation, workflow) by running the template's hooks/yaml-helper.sh, outside this skill's folder. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/quick-design/ 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/quick-design/ 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 32a4521f5290f459b84cf3500f86487d63b03d192281c392b7a023dcede03fb3 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 audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve automation and workflow, follows .claude/docs/automation-modes.md, and reads my project's GDDs and systems index under design/gdd/, prior specs under design/quick-specs/ and tuning data under assets/data/ — files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time it writes only after approval: the spec at design/quick-specs/[name]-[date].md after the draft is approved and a separate write ask is answered yes, and a GDD edit only after its own separate explicit approval showing the exact text change. It bypasses the /design-review and /review-all-gdds pipeline by design, and redirects oversized changes to /design-system. No third-party service, account or credential is named in the file. - Do not draft any spec, do not run any template hook, 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 quick-design folder into the agent's skills directory, in a folder named exactly "quick-design", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: quick-design), 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 and reads the template's design/ files), and that it writes its quick spec only after approval plus a separate write ask, with any GDD edit separately approved). 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.