Test Helpers

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 "Test Helpers" for me. 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. The skill itself generates engine-specific test helper libraries for the project: assertion utilities, factory functions and scene helpers written in the project's engine language (GDScript for Godot/GdUnit4, C# for Unity/NUnit, C++ for Unreal), placed in the engine's helper root (tests/helpers/ for Godot, Assets/Tests/EditMode/Helpers/ for Unity, Source/<Module>/Private/Tests/Helpers/ for Unreal) because that is the only place the test runner compiles them. It first resolves the engine, language and test framework from project.yaml or .claude/docs/technical-preferences.md (if the engine is not configured it stops and redirects to /setup-engine), reads a sample of existing tests plus the systems index, GDD sections and the TR registry to match the project's style and GDD bounds, and generates base helpers (scaffold mode), one system, or all systems. Two hard rules in the text: generated helpers must assert through the configured framework's assertion API, never a bare assert() (which aborts the run and is stripped in release builds), and when the framework's exact assertion call cannot be confirmed from the project's sources it generates NO helper rather than guessing (the worked Godot example carries a deliberate FAIL_IF placeholder for that one call). It presents the file list and asks before writing, and it never overwrites an existing helper file. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/test-helpers/ 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/test-helpers/ 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 b368b009a8abd6fd9282ce55b6a88aaccb512535cd9622b405b1f5a3f98053c1 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. Nothing in the folder is a program; the worked GDScript/C#/C++ helper code inside it is example text the skill adapts at use time, not code that runs at install. - 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 the automation mode by running the template's hooks/yaml-helper.sh (outside this skill's folder, absent standalone) and reads the template's project.yaml / technical-preferences.md, the project's existing tests, GDD sections and docs/architecture/tr-registry.yaml. All reads are local; no network service is named. - At use time it writes real code files, only after asking: new helper files in the engine's helper root (it never overwrites an existing file), whose assertions must go through the project's configured test framework; where the framework's assertion call cannot be confirmed it generates no helper instead of guessing. - Do not generate any helper, 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 test-helpers folder into the agent's skills directory, in a folder named exactly "test-helpers", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: test-helpers), 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, and what it does inside the template). 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.