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/docs/context-management.md
+11 -7
View File
@@ -25,7 +25,7 @@ Two regions, and the distinction is load-bearing:
| Region | Who reads it | Rule |
|--------|--------------|------|
| `<!-- STATUS -->` … `<!-- /STATUS -->` | `statusline.sh` (breadcrumb, Production+ only) | Keep the markers even when empty |
| `<!-- CHECKPOINT -->` … `<!-- /CHECKPOINT -->` | `session-start.sh` and `pre-compact.sh` | **Overwrite, never append.** Under ~25 lines — hooks inject it verbatim |
| `<!-- CHECKPOINT -->` … `<!-- /CHECKPOINT -->` | `session-start.sh` (every start, including after a compaction) | **Overwrite, never append.** Under ~25 lines — shown verbatim |
| Everything after `<!-- /CHECKPOINT -->` | humans, and an agent that wants detail | Free-form; no hook injects it |
The checkpoint holds: current task, next step, what it is blocked on, files in
@@ -76,9 +76,12 @@ After any disruption (compaction, crash, `/clear`), read the state file first.
When creating multi-section documents (design docs, architecture docs, lore entries):
1. Create the file immediately with a skeleton (all section headers, empty bodies)
1. Ask to create the file ("May I create [path] with the section skeleton?"), then
create it with every section header and empty bodies
2. Discuss and draft one section at a time in conversation
3. Write each section to the file as soon as it's approved
3. Write each section to the file as soon as it's approved (a skill that writes
once at the end, such as `/create-architecture`, records approved sections in
the session state instead)
4. Update the session state file after each section
5. After writing a section, previous discussion about that section can be safely
compacted — the decisions are in the file
@@ -124,10 +127,11 @@ Current helpers:
Two rules when adding one:
1. **A skill invoking a script needs `Bash` in `allowed-tools`**, or the step
silently no-ops. A skill that only needs *resolved config* does not — use the
documented `` !`cmd` `` body form, which is preprocessing and is not gated by
`allowed-tools` (see `.claude/docs/config-resolution.md`).
1. **Grant it the way `.claude/docs/config-resolution.md` shows.** `allowed-tools`
pre-approves commands; it does not restrict them — a skill without the grant
still runs the script, after a permission prompt. An injected `` !`cmd` `` in
the body is stricter: unapproved, it aborts the whole invocation, so it needs
the exact grant that doc gives.
2. **Emit observations, not verdicts.** A script that scores or judges will
eventually contradict a tier, mode, or per-system override it does not know
about. Report what is on disk and let the caller decide what it means.