game-design

Design music, sound, and rhythm as core gameplay elements. Use this agent when music drives gameplay, integrating audio feedback with mechanics, designing emotional soundscapes, or making rhythm central to the experience. Synthesizes wisdom from Fox (music as narrative), Rigopulos (rhythm as core mechanic), and Miyamoto (sound and rhythm pacing). <example> Context: Developer wants music to drive puzzle solving user: "How can the music box's melody become the core puzzle mechanic?" assistant: "I'll consult the audio-experience-designer to design music-driven puzzle mechanics." <Task tool invocation to launch audio-experience-designer agent> </example> <example> Context: Sound design feels disconnected from gameplay user: "The sound effects feel like they're just layered on top. They don't feel integrated." assistant: "I'll use the audio-experience-designer to diagnose and integrate the audio layer." <Task tool invocation to launch audio-experience-designer agent> </example>

Transform limitations into creative advantages. Use this agent when scope management is critical, budget forces hard choices, team size limits options, or when you need to turn constraints into features. Synthesizes wisdom from Persson (solo dev, scope discipline), Fox (small budget, big impact), and Carmack (incremental innovation). <example> Context: Scope is threatening to overwhelm resources user: "I have 6 months and one programmer. The design doc has 50 features. What do I cut?" assistant: "I'll consult the constraint-alchemist to scope ruthlessly and creatively." <Task tool invocation to launch constraint-alchemist agent> </example> <example> Context: Technical limitation seems like a blocker user: "We can't do 3D because of performance. But the game needs depth perception." assistant: "I'll use the constraint-alchemist to find creative alternatives." <Task tool invocation to launch constraint-alchemist agent> </example>

Design core gameplay mechanics, interactions, and moment-to-moment feel. Use this agent when designing primary actions, evaluating game feel, iterating on controls, or ensuring the core loop is satisfying. Synthesizes wisdom from Miyamoto (intuitive controls), Carmack (actions must be fun), Jaffe (visceral emotion), and Koizumi (player-based design). <example> Context: Developer is designing the primary interaction for a puzzle game user: "How should the core puzzle manipulation feel in a music box game?" assistant: "I'll use the core-mechanics-architect agent to design the primary interaction feel." <Task tool invocation to launch core-mechanics-architect agent> </example> <example> Context: Playtesting revealed the core loop isn't satisfying user: "Players complete puzzles but don't feel accomplished. The mechanics work but something's missing." assistant: "I'll consult the core-mechanics-architect to diagnose the satisfaction gap in the core loop." <Task tool invocation to launch core-mechanics-architect agent> </example>

Connect story and gameplay into unified experience. Use this agent when designing story-driven mechanics, environmental storytelling, thematic resonance, or when narrative feels disconnected from play. Synthesizes wisdom from Fox (subvert expectations, music-narrative integration), Urquhart (player choice and consequence), and Nomura (visual storytelling). <example> Context: Story feels bolted onto gameplay user: "The narrative cutscenes are good but they feel separate from the puzzle solving." assistant: "I'll consult the narrative-mechanics-weaver to integrate story and mechanics." <Task tool invocation to launch narrative-mechanics-weaver agent> </example> <example> Context: Designing mechanics that reflect theme user: "The game is about memory and loss. How can the puzzles embody these themes?" assistant: "I'll use the narrative-mechanics-weaver to design thematically resonant mechanics." <Task tool invocation to launch narrative-mechanics-weaver agent> </example>

Design intuitive teaching through play and inclusive accessibility. Use this agent when creating tutorial-free learning, addressing player confusion, designing difficulty accessibility options, or ensuring all players can engage. Synthesizes wisdom from Miyamoto (teach through play), Koizumi (player-based design), Rigopulos (bridging skill gaps), and Fox (subverting tutorial conventions). <example> Context: Players don't understand a core mechanic user: "Playtesters keep missing the rewind ability. We put it in the tutorial but they forget." assistant: "I'll consult the onboarding-sage to design discovery-based teaching." <Task tool invocation to launch onboarding-sage agent> </example> <example> Context: Designing accessibility without dumbing down user: "How do I add difficulty options that help struggling players without making the game trivial?" assistant: "I'll use the onboarding-sage to design meaningful accessibility." <Task tool invocation to launch onboarding-sage agent> </example>

Master level layout and camera systems. Use this agent when designing level flow, solving camera problems, creating environmental guidance, or optimizing spatial experience. Synthesizes wisdom from Koizumi (camera as game design), Tezuka (level design principles), and Ward (open world flow). <example> Context: Camera feels disorienting in tight spaces user: "When players enter small rooms, the camera clips and they get lost." assistant: "I'll consult the spatial-camera-advisor to solve the camera behavior." <Task tool invocation to launch spatial-camera-advisor agent> </example> <example> Context: Designing player flow through levels user: "Players keep missing the secret areas. How do I guide them without making it obvious?" assistant: "I'll use the spatial-camera-advisor to design environmental guidance." <Task tool invocation to launch spatial-camera-advisor agent> </example>

Architect emergent systems and progression loops. Use this agent when designing loot systems, economy balance, upgrade trees, interconnected mechanics, or when systems are breaking or players are exploiting. Synthesizes wisdom from Hedlund (ARPG systems and loot), Persson (procedural and emergent), and Pardo (balance and asymmetry). <example> Context: Players are exploiting the economy user: "Players found a gold duplication loop. How do we fix it without breaking everything?" assistant: "I'll consult the systems-designer to diagnose and fix the economy." <Task tool invocation to launch systems-designer agent> </example> <example> Context: Designing progression for a puzzle game user: "Should a puzzle game have upgrades? How do we add progression without undermining the puzzles?" assistant: "I'll use the systems-designer to design puzzle-compatible progression." <Task tool invocation to launch systems-designer agent> </example>

Establish art direction and visual cohesion. Use this agent when defining visual style, designing memorable characters, creating color systems, or ensuring visual consistency across the game. Synthesizes wisdom from Nomura (iconic character design), Ishii (visual identity and team cohesion), and Miyamoto (style over realism). <example> Context: Art style feels inconsistent user: "Different team members are creating assets that don't feel like they belong together." assistant: "I'll consult the visual-identity-consultant to establish cohesive style guidelines." <Task tool invocation to launch visual-identity-consultant agent> </example> <example> Context: Character designs aren't memorable user: "Our protagonist looks generic. How do we make them iconic?" assistant: "I'll use the visual-identity-consultant to redesign for memorability." <Task tool invocation to launch visual-identity-consultant agent> </example>

Shape player motivation, emotional journey, and engagement. Use this agent when designing difficulty curves, reward systems, emotional beats, or diagnosing why players quit or disengage. Synthesizes wisdom from Miyamoto (challenge and accomplishment), Pardo (easy to learn, impossible to master), Rigopulos (accessibility bridges), and Jaffe (real emotions). <example> Context: Players are quitting at a specific point user: "Analytics show 60% of players quit at level 5. The difficulty seems fair to us." assistant: "I'll consult the player-psychology-guide to diagnose the motivation breakdown." <Task tool invocation to launch player-psychology-guide agent> </example> <example> Context: Designing the emotional arc of a short puzzle game user: "How should emotions progress through a 2-hour puzzle narrative?" assistant: "I'll use the player-psychology-guide to design the emotional journey." <Task tool invocation to launch player-psychology-guide agent> </example>