| name | game-development |
| description | Game development orchestrator. Routes to platform-specific references based on project needs. Covers web, mobile, PC, VR/AR, 2D, 3D games, multiplayer networking, game design, art, and audio. |
Game Development
Orchestrator skill that provides core principles and routes to specialized references.
When to Use This Skill
You are working on a game development project. This skill teaches the PRINCIPLES of game development and directs you to the right reference based on context.
Reference Files
Platform-Specific
Dimension-Specific
| If the game is... | Load Reference |
|---|
| 2D (sprites, tilemaps) | 2d-games |
| 3D (meshes, shaders) | 3d-games |
Specialty Areas
Core Principles (All Platforms)
1. The Game Loop
Every game, regardless of platform, follows this pattern:
INPUT → Read player actions
UPDATE → Process game logic (fixed timestep)
RENDER → Draw the frame (interpolated)
Fixed Timestep Rule:
- Physics/logic: Fixed rate (e.g., 50Hz)
- Rendering: As fast as possible
- Interpolate between states for smooth visuals
2. Pattern Selection Matrix
| Pattern | Use When | Example |
|---|
| State Machine | 3-5 discrete states | Player: Idle→Walk→Jump |
| Object Pooling | Frequent spawn/destroy | Bullets, particles |
| Observer/Events | Cross-system communication | Health→UI updates |
| ECS | Thousands of similar entities | RTS units, particles |
| Command | Undo, replay, networking | Input recording |
| Behavior Tree | Complex AI decisions | Enemy AI |
Decision Rule: Start with State Machine. Add ECS only when performance demands.
3. Input Abstraction
Abstract input into ACTIONS, not raw keys:
"jump" → Space, Gamepad A, Touch tap
"move" → WASD, Left stick, Virtual joystick
Why: Enables multi-platform, rebindable controls.
4. Performance Budget (60 FPS = 16.67ms)
| System | Budget |
|---|
| Input | 1ms |
| Physics | 3ms |
| AI | 2ms |
| Game Logic | 4ms |
| Rendering | 5ms |
| Buffer | 1.67ms |
Optimization Priority:
- Algorithm (O(n²) → O(n log n))
- Batching (reduce draw calls)
- Pooling (avoid GC spikes)
- LOD (detail by distance)
- Culling (skip invisible)
5. AI Selection by Complexity
| AI Type | Complexity | Use When |
|---|
| FSM | Simple | 3-5 states, predictable behavior |
| Behavior Tree | Medium | Modular, designer-friendly |
| GOAP | High | Emergent, planning-based |
| Utility AI | High | Scoring-based decisions |
6. Collision Strategy
| Type | Best For |
|---|
| AABB | Rectangles, fast checks |
| Circle | Round objects, cheap |
| Spatial Hash | Many similar-sized objects |
| Quadtree | Large worlds, varying sizes |
Anti-Patterns (Universal)
| Don't | Do |
|---|
| Update everything every frame | Use events, dirty flags |
| Create objects in hot loops | Object pooling |
| Cache nothing | Cache references |
| Optimize without profiling | Profile first |
| Mix input with logic | Abstract input layer |
Routing Examples
Example 1: "I want to make a browser-based 2D platformer"
→ Load web-games for framework selection
→ Then 2d-games for sprite/tilemap patterns
→ Reference game-design for level design
Example 2: "Mobile puzzle game for iOS and Android"
→ Load mobile-games for touch input and stores
→ Use game-design for puzzle balancing
Example 3: "Multiplayer VR shooter"
→ vr-ar for comfort and immersion
→ 3d-games for rendering
→ multiplayer for networking
Remember: Great games come from iteration, not perfection. Prototype fast, then polish.
