mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 13:01:50 +00:00

Files

Donchitos 9a4243b373 Fix: rg --type gdscript is invalid — use --glob *.gd instead (#42 )

* Fix: document that rg --type gdscript is invalid, use --glob *.gd instead

Closes #37. ripgrep has no gdscript type — *.gd files are registered under
the gap type (GAP programming language). Using --type gdscript produces a
hard error, silently preventing any search from executing.

Added explicit warnings in two places:
- .claude/agents/godot-gdscript-specialist.md: new Tooling section with
  the correct Grep tool param (glob: "*.gd") and shell equivalent
- docs/engine-reference/godot/current-best-practices.md: new Tooling
  section agents read at version-check time

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Fix: propagate rg --glob *.gd tooling warning to all Godot agents

Closes the coverage gap identified in PR #42 review — the ripgrep
gdscript-type warning was only in godot-gdscript-specialist. Added
the same CRITICAL tooling section to godot-specialist,
godot-gdextension-specialist, godot-shader-specialist, and
godot-csharp-specialist so no Godot agent can silently misfire a search.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-02 20:40:23 +10:00

godot

Fix: rg --type gdscript is invalid — use --glob *.gd instead (#42 )

2026-05-02 20:40:23 +10:00

unity

Game Studio Agent Architecture — complete setup (Phases 1-7)

2026-02-13 21:04:24 +11:00

unreal

Game Studio Agent Architecture — complete setup (Phases 1-7)

2026-02-13 21:04:24 +11:00

README.md

Game Studio Agent Architecture — complete setup (Phases 1-7)

2026-02-13 21:04:24 +11:00

README.md

Engine Reference Documentation

This directory contains curated, version-pinned documentation snapshots for the game engine(s) used in this project. These files exist because LLM knowledge has a cutoff date and game engines update frequently.

Why This Exists

Claude's training data has a knowledge cutoff (currently May 2025). Game engines like Godot, Unity, and Unreal ship updates that introduce breaking API changes, new features, and deprecated patterns. Without these reference files, agents will suggest outdated code.

Structure

Each engine gets its own directory:

<engine>/
├── VERSION.md              # Pinned version, verification date, knowledge gap window
├── breaking-changes.md     # API changes between versions, organized by risk level
├── deprecated-apis.md      # "Don't use X → Use Y" lookup tables
├── current-best-practices.md  # New practices not in model training data
└── modules/                # Per-subsystem quick references (~150 lines max each)
    ├── rendering.md
    ├── physics.md
    └── ...

How Agents Use These Files

Engine-specialist agents are instructed to:

Read VERSION.md to confirm the current engine version
Check deprecated-apis.md before suggesting any engine API
Consult breaking-changes.md for version-specific concerns
Read relevant modules/*.md for subsystem-specific work

Maintenance

When to Update

After upgrading the engine version
When the LLM model is updated (new knowledge cutoff)
After running /refresh-docs (if available)
When you discover an API the model gets wrong

How to Update

Update VERSION.md with the new engine version and date
Add new entries to breaking-changes.md for the version transition
Move newly deprecated APIs into deprecated-apis.md
Update current-best-practices.md with new patterns
Update relevant modules/*.md with API changes
Set "Last verified" dates on all modified files

Quality Rules

Every file must have a "Last verified: YYYY-MM-DD" date
Keep module files under 150 lines (context budget)
Include code examples showing correct/incorrect patterns
Link to official documentation URLs for verification
Only document things that differ from the model's training data