mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 09:58:36 +00:00
DonchitosandClaude Opus 5
d05699707f
`project.yaml` at the repo root is now the single source of truth for a project's configuration, replacing `production/stage.txt`, `production/review-mode.txt` and `.claude/docs/technical-preferences.md` (all three still read as a fallback; nothing is force-deleted). **`modes.rigor` — one question instead of six.** `minimal`, `standard` or `full` fronts six knobs: `modes.workflow`, `docs.density`, `qa.level`, `modes.story_granularity`, `modes.review_mode` and `team.size`. It defaults to `minimal`, which is a change from 1.0's behaviour: the heavier tier was measured costing several times more to reach working code without producing a better result, and returning nothing when a fresh developer inherited the project. Pin `modes.rigor: standard` to keep 1.0's process level. Also in this release: - `/settings` to view or change any setting, and `project.local.yaml` for per-developer preferences that should not be committed. - `system_overrides` to hold one system to a higher standard than the rest of the project, and `testing.strict` to set per test type whether missing evidence blocks a story or warns. - A story that changes anything the player sees is not closed until the game has been launched, observed, and a screenshot retained in `production/qa/evidence/`. A parse check is not a run. This holds at every rigor level, including `minimal`, where automated tests are waived but the look is not. - The code root is engine-specific and enforced as such: Godot `src/`, Unity `Assets/`, Unreal `Source/<Module>/`. Two of the three will not build a project laid out any other way. - Migration tooling for existing projects: `.claude/scripts/migrate-v1-config.sh` converts a 1.0 layout, non-destructively by default, with a report to review before `--finalize` deletes anything. - Ask-before-write holds regardless of personal automation settings. Upgrading from 1.0 or earlier: see UPGRADING.md. Full list of changes: CHANGELOG.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016xvzG3i7pWQg4LjyDwWMXd
75 lines
2.8 KiB
Markdown
75 lines
2.8 KiB
Markdown
# Active Session State — [project or branch]
|
|
|
|
<!--
|
|
THE CONTRACT. Read this before editing the file or any hook that consumes it.
|
|
|
|
This file has TWO regions and they are not interchangeable:
|
|
|
|
1. The CHECKPOINT region below (STATUS + CHECKPOINT blocks) is the part
|
|
machines read. Hooks inject it verbatim into the context, so it is
|
|
BOUNDED BY CONSTRUCTION: keep it under ~25 lines. It is OVERWRITTEN on
|
|
every update, never appended to.
|
|
|
|
2. Everything after `<!-- /CHECKPOINT -->` is free-form narrative for humans
|
|
and for a returning agent that wants detail. No hook ever injects it, so
|
|
it may grow — but see Rotation below.
|
|
|
|
Why the split exists: before it, `active.md` was one append-only file doing
|
|
both jobs. It reached 712 lines / 44 KB, and each consumer invented its own
|
|
slice of it — the status line parsed for a STATUS block nothing wrote,
|
|
pre-compact injected `head -100` (12.7 KB), and session-start previewed
|
|
`tail -20`, the opposite end. They disagreed because there was no contract to
|
|
agree on. Now every consumer reads the named region.
|
|
|
|
ROTATION. When the narrative below grows past ~200 lines, move it to
|
|
`production/session-logs/` and start it fresh:
|
|
bash .claude/scripts/rotate-session-state.sh
|
|
Nothing is lost — and the commit history already records most of what the
|
|
narrative repeats.
|
|
-->
|
|
|
|
<!-- STATUS -->
|
|
Epic:
|
|
Feature:
|
|
Task:
|
|
<!-- /STATUS -->
|
|
|
|
<!-- CHECKPOINT -->
|
|
**Updated:** [YYYY-MM-DD]
|
|
**Branch:** `[branch]`
|
|
**Current task:** [one line — what is actively being worked on]
|
|
**Next step:** [one line — the very next action, concrete enough to resume cold]
|
|
**Blocked on:** [one line, or `nothing`]
|
|
**Files in progress:** [paths, comma-separated, or `none`]
|
|
**Open questions:** [one line each, or `none`]
|
|
<!-- /CHECKPOINT -->
|
|
|
|
---
|
|
|
|
## Notes
|
|
|
|
[Free-form. Decisions and their rationale, what was tried and rejected, context
|
|
that would be expensive to reconstruct. Not machine-read — write for the person
|
|
or agent picking this up cold.]
|
|
|
|
<!--
|
|
FIELD NOTES
|
|
|
|
STATUS block
|
|
Drives the status-line breadcrumb (`Combat System > Melee > Hitboxes`), and
|
|
only at Production / Polish / Release stage. All three fields are optional —
|
|
leave a field blank when it does not apply, and blank all three when there is
|
|
no active focus. Do not delete the markers themselves — `statusline.sh`
|
|
expects them to exist.
|
|
|
|
CHECKPOINT block
|
|
The recovery payload. `session-start.sh` shows it when a previous session
|
|
left state; `pre-compact.sh` injects it before compaction. Both read THIS
|
|
region and nothing else, which is what keeps the cost fixed no matter how
|
|
long the narrative gets.
|
|
|
|
Write it so a cold reader can resume without reading anything else. "Current
|
|
task: fixing the thing" is useless; "Current task: wiring modes.rigor into
|
|
/gate-check section 6.4" is not.
|
|
-->
|