mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 10:17:06 +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
64 lines
2.0 KiB
Markdown
64 lines
2.0 KiB
Markdown
> Section-authoring guidance, loaded by `/ux-design` for the ACTIVE MODE ONLY.
|
|
> Never load the other two — one mode applies per invocation.
|
|
|
|
# Section Guidance — Interaction Pattern Library Mode
|
|
|
|
|
|
Pattern library authoring is additive and catalog-driven, not linear.
|
|
|
|
#### Phase 1: Catalog Existing Patterns
|
|
|
|
Glob `design/ux/*.md` (excluding `interaction-patterns.md`) and read the Component
|
|
Inventory and Interaction Map sections of each spec. Extract every interaction
|
|
pattern used.
|
|
|
|
Present the extracted list: "Based on existing UX specs, these patterns are already
|
|
in use in the game:"
|
|
- [Pattern name]: used in [screen], [screen]
|
|
- [etc.]
|
|
|
|
Ask: "Are there patterns you know exist but aren't in existing specs yet? List any
|
|
additional ones now."
|
|
|
|
---
|
|
|
|
#### Phase 2: Formalize Each Pattern
|
|
|
|
For each pattern (existing or new), document:
|
|
|
|
```markdown
|
|
### [Pattern Name]
|
|
|
|
**Category**: Navigation / Input / Feedback / Data Display / Modal / Overlay / [other]
|
|
**Used In**: [list of screens]
|
|
|
|
**Description**: [One paragraph explaining what this pattern is and when to use it]
|
|
|
|
**Specification**:
|
|
- [Component behavior]
|
|
- [Input mapping]
|
|
- [Visual/audio feedback]
|
|
- [Accessibility requirements for this pattern]
|
|
|
|
**When to Use**: [Conditions where this pattern is appropriate]
|
|
**When NOT to Use**: [Conditions where another pattern is more appropriate]
|
|
|
|
**Reference**: [Screenshot path or ASCII example, if available]
|
|
```
|
|
|
|
Work through patterns in groups. Use `AskUserQuestion`:
|
|
- "How do you want to work through these patterns?"
|
|
- Options: "Draft the first batch from existing specs (faster)", "Define them one by one (more control)", "Start with the most-used pattern first"
|
|
|
|
---
|
|
|
|
#### Phase 3: Identify Gaps
|
|
|
|
After cataloging known patterns, ask:
|
|
- "Are there screens or interactions planned that would need patterns not yet
|
|
in this library?"
|
|
- "Are there any patterns in existing specs that feel inconsistent with each
|
|
other and should be consolidated?"
|
|
|
|
Document gaps in the Gaps section for follow-up.
|