Files
Claude-Code-Game-Studios/project.yaml
T
DonchitosandClaude Opus 5.5 b21fa0f7f2 Release 1.1.2 — the default path works end to end
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
2026-09-29 21:32:19 +10:00

28 lines
1.1 KiB
YAML

# CCGS project configuration — single source of truth for project settings.
# See .claude/docs/effects-map.md for full schema.
schema_version: 1
framework:
version: 1.1.2
last_upgraded: 2026-09-25
# NOTE: this template ships with no `modes:` block, and the six knobs below must
# never be added to one.
#
# `/start` DOES add `modes.rigor` and `modes.automation` here — that is its job,
# and a `modes:` block containing those two is the expected state of a configured
# project, not a mistake.
#
# What must stay absent is the six knobs `modes.rigor` FRONTS:
# `modes.review_mode`, `modes.workflow`, `docs.density`, `qa.level`,
# `modes.story_granularity` and `team.size`. Seeding any of them in this file
# pins that value and shadows the rigor expansion, so `/start` asking "what are
# you building?" would stop changing anything. `/start` Phase 3c documents the
# same rule for the file it writes.
#
# Per-developer preferences belong in `project.local.yaml` (gitignored), not
# here. `/settings --local <key>=<value>` writes there; `/settings <key>=<value>`
# edits this file. See `.claude/docs/config-resolution.md` for the full
# precedence order.