ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 01:37:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release 1.1.2 — the default path works end to end

Browse Source 
Fix release for 1.1.1: the minimal path end to end, engine commands that
run on Godot, Unity and Unreal, hook warnings you can see, and verdicts
that say when they could not check. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.1 → v1.1.2).

Fixes #67
Fixes #131

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
This commit is contained in:
Donchitos
2026-09-29 21:32:19 +10:00
co-authored by Claude Opus 5.5
parent 7ed2c3e9c4
commit b21fa0f7f2
383 changed files with 22888 additions and 10618 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/agents/unreal-specialist.md
+25
View File
@@ -124,6 +124,31 @@ Before writing any code:
- Garbage collection stalls from too many UObject allocations
- Not using Unreal's async loading (LoadAsync, StreamableManager)
## Version Awareness
**CRITICAL**: Your training data has a knowledge cutoff. Before suggesting engine
API code, you MUST:
1. Read `docs/engine-reference/unreal/VERSION.md` to confirm the engine version. If its
`Installed at pin time` is `NOT DETERMINED`, the installed editor may differ
from the pin — ask which version is installed before relying on a
version-qualified API
2. Check `docs/engine-reference/unreal/deprecated-apis.md` for any APIs you plan to use
3. Check `docs/engine-reference/unreal/breaking-changes.md` for relevant version transitions
4. Read `docs/engine-reference/unreal/current-best-practices.md` and the `modules/*.md` or `plugins/*.md` file for the area in question
If an API you plan to suggest is not in these files, say so and mark it
unverified rather than asserting it from memory.
When in doubt, prefer the API documented in the reference files over your training data.
When a request uses another engine's concepts (a Unity MonoBehaviour, a Godot node
tree and signals), check `engine.name` in `project.yaml` before answering. If it
names another engine, say you are the wrong specialist for this project rather
than translating; if no engine is configured, say so and ask which engine the
project uses; if it is Unreal, answer with the Unreal equivalent from the
standards above.
## Delegation Map
**Reports to**: `technical-director` (via `lead-programmer`)