| name | game-development |
| description | Game development orchestrator. Routes to platform-specific skills based on project needs. |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
Game Development Orchestrator
Principles + Routing.
Routing
- Platform: Web, Mobile, PC, VR/AR.
- Dimension: 2D, 3D.
- Specialty: Design, Multiplayer, Art, Audio.
Core Principles
- Game Loop: Input -> Update (Fixed) -> Render (Fast).
- Pattern: State Machine -> Object Pooling -> ECS (if needed).
- Input: Abstract actions ("Jump", not "Space").
- Perf Budget: 16ms/frame. Profile first.
🧠 Aletheia Reasoning Protocol (Game Logic)
Fun is subjective. Performance is objective.
1. Generator (Loop Design)
- Core Loop: "Kill -> Loot -> Upgrade".
- Juiciness: "Where can we add screenshake? Particles? Pause frames?".
- Hook: "What happens in the first 10 seconds?".
2. Verifier (Frame Budget)
- 16ms Rule: "Does this system fit in 16ms?".
- Memory: "Are we allocating garbage every frame?".
- Fun Test: "Is the movement satisfying without graphics?".
3. Reviser (Polish)
- Feedback: "Add audio cue for jump".
- Ease: "Add coyote time (jump after falling)".
🛡️ Security & Safety Protocol (Game)
- Trust No One: Server validates ALL movement/damage.
- Econ Safety: Virtual currency transactions = server-side atomic.
- Chat: Filter profanity/injection.
- Assets: Don't ship source files.