| name | unreal-game-development |
| description | Use when building or restructuring an Unreal Engine game with C++, Blueprints, Gameplay Framework classes, replication, assets, packaging, automation, or Unreal-specific profiling and release evidence. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Unreal Game Development
Build version-pinned Unreal projects with deliberate C++/Blueprint boundaries, explicit gameplay ownership, automated tests, and release-like packaged evidence.
Use When
- The project uses Unreal Engine, Gameplay Framework, C++, Blueprints, replication, Unreal assets, or Unreal packaging.
Do Not Use When
- Multiplayer architecture is the primary decision; load
online-multiplayer-and-game-backend first.
- The exact engine/plugin versions are unknown.
Required Inputs
Engine/source distribution and version, plugins, target platforms/hardware, network topology, module/asset map, performance budgets, build farm, acceptance criteria, and tests.
Workflow
- Inspect
.uproject, modules, targets, plugins, config, maps, assets, source, automation, and packaging settings.
- Record boundaries among engine framework classes, C++ domain/components, Blueprints, data assets, subsystems, and online services.
- Define server/client authority, replicated properties, RPC contracts, relevance/update budgets, and late-join state when networked.
- Enforce asset naming/dependency and map/cook rules; validate redirectors and unintended hard references.
- Add automation for pure logic, gameplay integration, multiplayer network profiles, cook/package, and target-hardware smoke tests.
- Profile and retain packaged-build CPU/GPU/network/memory evidence; preserve symbols and manifests.
Quality Standards
- Blueprint accessibility is not a reason to hide ownership, authority, or failure handling.
- Exact APIs follow pinned official Unreal documentation, not copied book snippets.
- Editor/PIE success does not replace packaged target or network-condition testing.
Outputs
Unreal architecture and version manifest; module/Blueprint contract; authority/replication spec; asset validation report; automation results; packaged build evidence.
References
