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
34 lines
1.5 KiB
Markdown
34 lines
1.5 KiB
Markdown
# Docs Directory
|
|
|
|
When authoring or editing files in this directory, follow these standards.
|
|
|
|
## Architecture Decision Records (`docs/architecture/`)
|
|
|
|
Use the ADR template: `.claude/docs/templates/architecture-decision-record.md`
|
|
|
|
**Required sections:** Title, Status, Context, Decision, Consequences,
|
|
ADR Dependencies, Engine Compatibility, GDD Requirements Addressed
|
|
|
|
**Status lifecycle:** `Proposed` → `Accepted` → `Superseded`
|
|
- Never skip `Accepted` — stories referencing a `Proposed` ADR are auto-blocked
|
|
- Use `/architecture-decision` to create ADRs through the guided flow
|
|
|
|
**TR Registry:** `docs/architecture/tr-registry.yaml`
|
|
- Stable requirement IDs (e.g. `TR-movement-001`) that link GDD requirements to stories
|
|
- Never renumber existing IDs — only append new ones
|
|
- Updated by `/architecture-review` Phase 8
|
|
|
|
**Control Manifest:** `docs/architecture/control-manifest.md`
|
|
- Flat programmer rules sheet: Required / Forbidden / Guardrails per layer
|
|
- Date-stamped `Manifest Version:` in header
|
|
- Stories embed this version; `/story-done` checks for staleness
|
|
|
|
**Validation:** Run `/architecture-review` after completing a set of ADRs.
|
|
|
|
## Engine Reference (`docs/engine-reference/`)
|
|
|
|
Version-pinned engine API snapshots. **Always check here before using any
|
|
engine API** — the LLM's training data predates the pinned engine version.
|
|
|
|
Current engine: see `docs/engine-reference/<engine>/VERSION.md` (`<engine>` is `godot`, `unity` or `unreal`, matching `engine.name` in `project.yaml`)
|