Game Developer guides Claude through game programming in five steps: analyze requirements, design the architecture, implement mechanics, optimize and test. Two checkpoints set a frame time of 16 ms or less under the profiler and require latency and desync tests for multiplayer.
Five reference files cover Unity patterns, Unreal C++, ECS and game patterns, performance optimization and multiplayer networking. The SKILL.md includes C# code for an object pool, component caching and a state machine.
What You Get
- Core systems as ECS components, MonoBehaviours or Unreal Actors
- Data structures such as ScriptableObjects, structs and configs
- Performance notes covering CPU, GPU and memory
- Networking code for client-server play, prediction and lag compensation
- A short explanation of the architecture choices
Common Use Cases
- Adding object pooling to bullets, effects or enemies
- Structuring character logic with a state machine
- Building client-side prediction and server-side rewind for multiplayer
- Fixing frame drops with batching, LOD and culling
What Makes It Unique
The rules are concrete engine habits: no GetComponent or Find calls in Update, no allocation in Update or FixedUpdate, CompareTag for tags, ScriptableObjects for game values and Time.deltaTime for movement. It covers both Unity C# and Unreal C++ and has a networking reference with interest management and delta compression.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. The workflow asks you to run the Unity Profiler or Unreal Insights and to run cross-platform and multiplayer stress tests, which the agent cannot do for you. The skill gives C# and C++ code that the agent writes into your game project. It does not run shell commands, fetch web pages or call outside APIs by itself.