ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 04:51:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release v0.4.0: /consistency-check, skill fixes, genre-agnostic agents

Browse Source 
New skill: /consistency-check — cross-GDD entity registry scanner
New registries: design/registry/entities.yaml, docs/registry/architecture.yaml
Skill fixes: no-arg guards, verdict keywords, AskUserQuestion gates on all team-* skills
Agent fixes: genre-agnostic language in game-designer, systems-designer, economy-designer, live-ops-designer
Docs: skill/template counts corrected, stale references cleaned up

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-27 20:06:33 +11:00
parent 04ed5d5c36
commit 6c041ac1be
108 changed files with 2745 additions and 1005 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
.claude/skills/setup-engine/SKILL.md
View File

@@ -74,8 +74,12 @@ Once the engine is chosen:
## 4. Update CLAUDE.md Technology Stack
Read `CLAUDE.md` and update the Technology Stack section. Replace the
`[CHOOSE]` placeholders with the actual values:
Read `CLAUDE.md` and show the user the proposed Technology Stack changes.
Ask: "May I write these engine settings to `CLAUDE.md`?"
Wait for confirmation before making any edits.
Update the Technology Stack section, replacing the `[CHOOSE]` placeholders with the actual values:
**For Godot:**
```markdown
@@ -317,6 +321,10 @@ Create the full reference doc set by searching the web:
- Deprecated APIs with replacements
- New features and best practices
Ask: "May I create the engine reference docs under `docs/engine-reference/<engine>/`?"
Wait for confirmation before writing any files.
3. **Create the full reference directory**:
```
docs/engine-reference/<engine>/
@@ -338,7 +346,9 @@ Create the full reference doc set by searching the web:
## 8. Update CLAUDE.md Import
Update the `@` import under "Engine Version Reference" to point to the
Ask: "May I update the `@` import in `CLAUDE.md` to point to the new engine reference?"
Wait for confirmation, then update the `@` import under "Engine Version Reference" to point to the
correct engine:
```markdown
@@ -354,6 +364,8 @@ Godot to Unity), update it.
## 9. Update Agent Instructions
Ask: "May I add a Version Awareness section to the engine specialist agent files?" before making any edits.
For the chosen engine's specialist agents, verify they have a
"Version Awareness" section. If not, add one following the pattern in
the existing Godot specialist agents.
@@ -512,6 +524,8 @@ Next Steps:
---
Verdict: **COMPLETE** — engine configured and reference docs populated.
## Guardrails
- NEVER guess an engine version — always verify via WebSearch or user confirmation