mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 09:48:34 +00:00

Files

T

DonchitosandClaude Opus 5 d05699707f Release 1.1.0 — one config file, and a process weight you choose

`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

2026-09-23 12:25:11 +10:00

1.1 KiB

Raw Blame History

Agent Teams (experimental — opt-in)

On-demand reference. Demoted out of coordination-rules.md (an always-loaded CLAUDE.md import) in v1.1 — read this when actually considering a team, not on every turn.

Multiple independent Claude Code sessions running simultaneously, coordinated via a shared task list. Each session has its own context window and token budget. Requires the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 environment variable.

Use agent teams when

Work spans multiple subsystems that will not touch the same files
Each workstream would take >30 minutes and benefits from true parallelism
A senior agent (technical-director, producer) needs to coordinate 3+ specialist sessions working on different epics simultaneously

Do not use agent teams when

One session's output is required as input for another (use sequential subagents)
The task fits in a single session's context (use subagents instead)
Cost is a concern — each team member burns tokens independently

Current status

Opt-in via CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. Document first usage here when adopted.

1.1 KiB Raw Blame History

Agent Teams (experimental — opt-in)

Use agent teams when

Do not use agent teams when

Current status

1.1 KiB

Raw Blame History