mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
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
This commit is contained in:
co-authored by
Claude Opus 5
parent
984023ddac
commit
d05699707f
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/art-director.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references visual identity, art bible, asset standards — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; image review capability if supported; no Bash unless asset pipeline checks are justified
|
||||
- [ ] Model tier is `claude-sonnet-4-6` (NOT Opus — coordination-rules.md assigns Sonnet to art-director)
|
||||
- [ ] Model tier is `claude-sonnet-5` (NOT Opus — coordination-rules.md assigns Sonnet to art-director)
|
||||
- [ ] Agent definition does not claim authority over UX interaction flows or audio direction
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/creative-director.md` frontmatte
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references creative vision, pillars, GDD alignment — not generic)
|
||||
- [ ] `allowed-tools:` list is read-heavy; should not include Bash unless justified by a creative workflow need
|
||||
- [ ] Model tier is `claude-opus-4-6` per coordination-rules.md (directors with gate synthesis = Opus)
|
||||
- [ ] Model tier is `claude-opus-4-8` per coordination-rules.md (directors with gate synthesis = Opus)
|
||||
- [ ] Agent definition does not claim authority over technical architecture or production scheduling
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/producer.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references scope, sprint, milestone, production — not generic)
|
||||
- [ ] `allowed-tools:` list is primarily read-focused; Bash only if sprint/milestone files require parsing
|
||||
- [ ] Model tier is `claude-opus-4-6` per coordination-rules.md (directors with gate synthesis = Opus)
|
||||
- [ ] Model tier is `claude-opus-4-8` per coordination-rules.md (directors with gate synthesis = Opus)
|
||||
- [ ] Agent definition does not claim authority over design decisions or technical architecture
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/technical-director.md` frontmatt
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references architecture, feasibility, ADR — not generic)
|
||||
- [ ] `allowed-tools:` list may include Read for architecture documents; Bash only if required for technical checks
|
||||
- [ ] Model tier is `claude-opus-4-6` per coordination-rules.md (directors with gate synthesis = Opus)
|
||||
- [ ] Model tier is `claude-opus-4-8` per coordination-rules.md (directors with gate synthesis = Opus)
|
||||
- [ ] Agent definition does not claim authority over game design decisions or creative direction
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/audio-director.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references music direction, sound design, mix, audio implementation — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; no Bash unless audio asset pipeline checks are justified
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over visual design, code implementation, or narrative content
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/game-designer.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references core loop, progression, combat rules, economy, player-facing design — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; includes Read for GDDs and design docs; no Bash unless design tooling requires it
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over code implementation, visual art style, or standalone narrative lore decisions
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/lead-programmer.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references code architecture, feasibility, code review, coding standards — not generic)
|
||||
- [ ] `allowed-tools:` list includes Read for source files; Bash may be included for static analysis or test runs; no write access outside `src/` without explicit delegation
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over game design, creative direction, or production scheduling
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/level-designer.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references level layout, encounter design, pacing, environmental storytelling — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; includes Read for level design documents and GDDs; no Bash unless level tooling requires it
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over narrative dialogue, AI behavior code, or visual art style
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/narrative-director.md` frontmatt
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references story, character, world-building, consistency — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; includes Read for lore documents, GDDs, and narrative docs; no Bash unless justified
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over visual style, technical systems, or production scheduling
|
||||
|
||||
---
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/qa-lead.md` frontmatter:
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references test strategy, story readiness, coverage, bug triage — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; may include Read for story files, test files, and coding-standards; Bash only if running test commands is required
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over implementation decisions or game design
|
||||
|
||||
---
|
||||
@@ -57,7 +57,7 @@ Verified by reading the agent's `.claude/agents/qa-lead.md` frontmatter:
|
||||
- [ ] Does not abandon the coverage requirement — asks for a deterministic alternative if the current approach is ruled flaky
|
||||
|
||||
### Case 5: Context pass — uses provided context
|
||||
**Scenario:** Agent receives a gate context block that includes the coding-standards.md testing standards section, which specifies: Logic stories require blocking automated unit tests, Visual/Feel stories require screenshots + lead sign-off (advisory), Config/Data stories require smoke check pass (advisory). A story classified as "Logic" type is submitted with only a manual walkthrough document as evidence.
|
||||
**Scenario:** Agent receives a gate context block that includes the coding-standards.md testing standards section, which specifies: Logic stories require blocking automated unit tests, Visual/Feel stories require a blocking retained screenshot + lead sign-off, Config/Data stories require smoke check pass (advisory). A story classified as "Logic" type is submitted with only a manual walkthrough document as evidence.
|
||||
**Expected:** Assessment references the specific test evidence requirements from coding-standards.md, identifies that a "Logic" story requires an automated unit test (not just a manual walkthrough), and returns INADEQUATE with the specific requirement cited.
|
||||
**Assertions:**
|
||||
- [ ] References the specific story type classification ("Logic") from the provided context
|
||||
|
||||
@@ -14,7 +14,7 @@ Verified by reading the agent's `.claude/agents/systems-designer.md` frontmatter
|
||||
|
||||
- [ ] `description:` field is present and domain-specific (references formulas, progression curves, balance math, economy — not generic)
|
||||
- [ ] `allowed-tools:` list is read-focused; may include Bash for formula evaluation scripts if the project uses them; no write access outside `design/balance/` without delegation
|
||||
- [ ] Model tier is `claude-sonnet-4-6` per coordination-rules.md
|
||||
- [ ] Model tier is `claude-sonnet-5` per coordination-rules.md
|
||||
- [ ] Agent definition does not claim authority over narrative, visual design, or conceptual mechanic rule ownership
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user