mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +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
2.0 KiB
2.0 KiB
Gate definition, loaded by
/gate-checkfor the TARGET PHASE ONLY. Never load the other five — one gate applies per invocation.
Gate: Systems Design → Technical Setup
Required Artifacts:
- Systems index exists at
design/gdd/systems-index.mdwith at least MVP systems enumerated - All MVP-tier GDDs exist in
design/gdd/and individually pass/design-review - A cross-GDD review report exists in
design/gdd/(from/review-all-gdds)
Quality Checks:
- All MVP GDDs pass individual design review (8 required sections, no MAJOR REVISION NEEDED verdict)
/review-all-gddsverdict is not FAIL (cross-GDD consistency and design theory checks pass)- All cross-GDD consistency issues flagged by
/review-all-gddsare resolved or explicitly accepted - System dependencies are mapped in the systems index and are bidirectionally consistent
- MVP priority tier is defined
- No stale GDD references flagged (older GDDs updated to reflect decisions made in later GDDs)
Workflow tier reductions
The checklist above is the full baseline. At lower tiers apply the
reduction for the resolved tier; items not named keep their status above.
Reductions only ever relax a requirement — workflow_overrides is the
only thing that adds one.
full— systems-index + all MVP GDDs at 8 sections + cross-GDD review report all requiredstandard— MVP GDDs validated at the 5 standard sections (+ conditional Formulas); cross-GDD review report → recommendedminimal— gate not applicable — no gate between brief and code; auto-PASS with a note (see below)
minimal"not applicable" gate. The Systems Design → Technical Setup gate has no meaning atminimal(no GDDs exist by design). Return a PASS verdict with the note: "No design gate at minimal workflow — minimal skips the Systems Design phase; advancing brief → code." The Section 6 stage write still applies on user confirmation. Do NOT flag absent GDDs as blockers.