mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
DonchitosandClaude Opus 5.5
be8993bbc5
Fix release for 1.1.2: the 14 longest skills keep their later phases after a compaction, a question nobody answered is never taken as an answer, settings read the same from a subfolder, the commit check works for a project in a subfolder of a larger repository, every skill opens with a title, and the shipped allow rules no longer approve deleting a branch or writing files without asking. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.2 → v1.1.3). Refs #83 Refs #133 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
1.1 KiB
1.1 KiB
/create-architecture — Phase 2: Module Ownership Map
Part of
/create-architecture.SKILL.mdnames when to read this file; the settings it resolved and the rules under its later headings still apply here.
Phase 2: Module Ownership Map
For each module defined in Phase 1, define ownership:
- Owns: what data and state this module is solely responsible for
- Exposes: what other modules may read or call
- Consumes: what it reads from other modules
- Engine APIs used: which specific engine classes/nodes/signals this module calls directly (with version and risk level noted)
Format as a table per layer, then as an ASCII dependency diagram.
Engine awareness check: For every engine API listed, verify against the relevant module reference doc. If an API is post-cutoff, flag it:
⚠️ [ClassName.method()] — Godot 4.6 (post-cutoff, HIGH risk)
Verified against: docs/engine-reference/godot/modules/[domain].md
Behaviour confirmed: [yes / NEEDS VERIFICATION]
Get user approval on the ownership map, then record it in
production/session-state/active.md; it is written at Phase 7.