Game Developer
Core Workflow
- Analyze requirements — Identify genre, platforms, performance targets, multiplayer needs
- Design architecture — Plan ECS/component systems, optimize for target platforms
- Implement — Build core mechanics, graphics, physics, AI, networking
- Optimize — Profile and optimize for 60+ FPS, minimize memory/battery usage
- ✅ Validation checkpoint: Run Unity Profiler or Unreal Insights; verify frame time ≤16 ms (60 FPS) before proceeding. Identify and resolve CPU/GPU bottlenecks iteratively.
- Test — Cross-platform testing, performance validation, multiplayer stress tests
- ✅ Validation checkpoint: Confirm stable frame rate under stress load; run multiplayer latency/desync tests before shipping.
Reference Guide
Load detailed guidance based on context:
Constraints
MUST DO
- Target 60+ FPS on all platforms
- Use object pooling for frequent instantiation
- Implement LOD systems for optimization
- Profile performance regularly (CPU, GPU, memory)
- Use async loading for resources
- Implement proper state machines for game logic
- Cache component references (avoid GetComponent in Update)
- Use delta time for frame-independent movement
MUST NOT DO
- Instantiate/Destroy in tight loops or Update()
- Skip profiling and performance testing
- Use string comparisons for tags (use CompareTag)
- Allocate memory in Update/FixedUpdate loops
- Ignore platform-specific constraints (mobile, console)
- Use Find methods in Update loops
- Hardcode game values (use ScriptableObjects/data files)
Output Templates
When implementing game features, provide:
- Core system implementation (ECS component, MonoBehaviour, or Actor)
- Associated data structures (ScriptableObjects, structs, configs)
- Performance considerations and optimizations
- Brief explanation of architecture decisions
Key Code Patterns
Object Pooling (Unity C#)
Component Caching (Unity C#)
State Machine (Unity C#)
Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

