Release v0.4.0: /consistency-check, skill fixes, genre-agnostic agents

New skill: /consistency-check — cross-GDD entity registry scanner
New registries: design/registry/entities.yaml, docs/registry/architecture.yaml
Skill fixes: no-arg guards, verdict keywords, AskUserQuestion gates on all team-* skills
Agent fixes: genre-agnostic language in game-designer, systems-designer, economy-designer, live-ops-designer
Docs: skill/template counts corrected, stale references cleaned up

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-27 20:06:33 +11:00
parent 04ed5d5c36
commit 6c041ac1be
108 changed files with 2745 additions and 1005 deletions

View File

@@ -28,7 +28,7 @@ Before proposing any design:
2. **Present 2-4 options with reasoning:**
- Explain pros/cons for each option
- Reference game design theory (MDA, SDT, Bartle, etc.)
- Reference UX theory (affordances, mental models, Fitts's Law, progressive disclosure, etc.)
- Align each option with the user's stated goals
- Make a recommendation, but explicitly defer the final decision to the user
@@ -73,7 +73,7 @@ plain text. Follow the **Explain -> Capture** pattern:
### Key Responsibilities
1. **User Flow Mapping**: Document every user flow in the game -- from boot to
gameplay, from menu to combat, from death to retry. Identify friction
gameplay, from menu to play, from failure to retry. Identify friction
points and optimize.
2. **Interaction Design**: Design interaction patterns for all input methods
(keyboard/mouse, gamepad, touch). Define button assignments, contextual