ue5 game dev squad
ue5 game dev squad
8-agent expert team for UE5 development — Design, Architecture, VFX, Netcode, UI, Level, Performance
UE5 Game Dev Squad — Expert Agents for Unreal Engine 5
8 specialist AI agents. Every domain of UE5 game development. Zero blind spots. Works standalone or as the strategic brain behind UNREAL-FORGE.
Why a Squad?
Generic AI gives you generic answers. Ask it about UE5 networking and you get a Wikipedia summary. Ask @netcode and you get a server-authoritative replication map with RPC flows, ownership chains, and anti_bypass validation — because it's built on Cedric Neukirchen's Multiplayer Network Compendium, the most cited UE networking resource in the community.
Every agent in this squad is built on real practitioner knowledge, not training data averages.
The Agents
| Agent | Domain | Built On | What They Actually Do |
|---|---|---|---|
| @ue5-chief | Orchestrator | Routing logic | Reads your question, sends it to the right specialist. Coordinates multi-domain tasks. |
| @designer | Game Design | Jesse Schell's Lenses + Tracy Fullerton's Playcentric Method | Turns vague ideas into structured GDDs with core/meta/progression loops, mechanic balance, and UE5 system mapping. |
| @architect | C++ Architecture | Tom Looman + Alex Forsythe | Designs class hierarchies, chooses between Component/Subsystem/Interface patterns, catches anti-patterns like deep inheritance or God classes. |
| @worldbuilder | Level Design | Alex Galuzin (World of Level Design) | Plans spatial layouts, player flow, blockout guides with real measurements, lighting moods, NavMesh requirements, World Partition strategy. |
| @vfx-artist | VFX & Materials | Ashif Ali (CGHOW) + Ben Cloward | Breaks any VFX into Niagara emitters, designs material node graphs, knows when to use GPU vs CPU sim, catches overdraw problems. |
| @netcode | Multiplayer | Cedric Neukirchen's Compendium + Alex Forsythe | Architects replication strategies, RPC flows, server authority patterns, movement prediction, and session management. |
| @ui-architect | UI/UX | YawLighthouse (UMG-Slate Compendium) | Designs widget hierarchies with BindWidget patterns, event-driven data binding, CommonUI for cross-platform, responsive anchoring. |
| @optimizer | Performance | Tom Looman's Optimization Course (65+ lessons) | Profiles before optimizing. Identifies CPU vs GPU bottleneck. Prioritized fix plans with expected ms savings. |
Key Differentiators
Real Frameworks, Not Generic Advice
Each agent carries documented methodologies from the UE5 community's best:
- @designer applies Schell's 100+ Lenses to evaluate your mechanics ("Does this create flow state? Is there triangularity in risk/reward?")
- @architect uses Looman's component-composition-first approach, not textbook OOP
- @netcode follows Neukirchen's replication patterns used in production multiplayer games
- @optimizer never says "optimize it" — always says "profile with
stat unitfirst, then fix the biggest ms cost"
Anti-Pattern Detection
Every agent actively catches mistakes in their domain:
| Agent | What They Catch |
|---|---|
| @architect | Deep inheritance chains, God classes, direct cross-system references, legacy input |
| @netcode | Client-trusted state, reliable RPCs on cosmetics, missing GetLifetimeReplicatedProps |
| @ui-architect | Per-frame property bindings, missing anchors, tick-driven UI updates |
| @optimizer | Unnecessary ticks, CPU particles over 1K, full-res textures on small props |
| @vfx-artist | Unbounded Niagara systems, translucent overdraw, master material edits |
| @worldbuilder | Missing NavMesh, empty spaces, flat levels, World Partition on small maps |
| @designer | Feature bloat, mechanics without purpose, designing for designer not player |
Orchestrated Multi-Agent Workflows
@ue5-chief doesn't just route — it coordinates. When your question spans domains:
You: "I need a multiplayer battle royale with 64 players"
@ue5-chief coordinates:
1. @designer → Core loop, shrinking zone mechanic, loot economy
2. @architect → Class hierarchy with replication in mind
3. @netcode → 64-player dedicated server architecture, relevancy culling
4. @optimizer → Performance budget for 64 concurrent players
→ Synthesis: Unified architecture document
FORGE Integration (Ecosystem Mode)
When paired with UNREAL-FORGE, the Squad becomes the strategic layer that informs code generation:
Without Squad: Concept → FORGE decides architecture → Code
With Squad: Concept → Squad experts refine → FORGE generates informed code
The difference: @architect catches that your inventory should be a Component (not an Actor), @netcode specifies which properties need COND_OwnerOnly, and @optimizer flags that the EnemySpawner needs an object pool. FORGE then generates code with all these decisions baked in.
Standalone Value
Each agent is a deep-domain consultant that works without FORGE:
@architect → "How should I structure a GAS-based ability system?"
→ Full class hierarchy with AbilitySystemComponent,
GameplayAbilities, GameplayEffects, AttributeSets,
and the delegate patterns to wire them together.
@netcode → "How do I sync inventory between client and server?"
→ Replication strategy with COND_OwnerOnly,
Server RPCs for item use, OnRep for UI updates,
and validation logic to prevent item duplication.
@optimizer → "My open world runs at 25fps"
→ Step-by-step: run stat unit → identify GPU bound →
check draw calls with stat scenerendering →
enable Nanite on static meshes → set HLOD distances →
expected improvement: +15-20fps
Slash Commands
/UE5-SQUAD:consult — Route any question to the best specialist
/UE5-SQUAD:design-game — Full Game Design Document from a concept
/UE5-SQUAD:review — Multi-agent architecture & code review
Structured Tasks
The squad includes 6 ready-made task templates for common workflows:
| Task | What It Does |
|---|---|
design-game-concept | Concept → GDD with loops, mechanics, UE5 system mapping |
review-architecture | Multi-perspective code review (architecture + performance + networking) |
plan-multiplayer | Complete replication map, RPC flows, authority patterns |
optimize-project | Profiling guidance → bottleneck identification → prioritized fixes |
design-level | Spatial layout, player flow, blockout guide, lighting plan |
design-vfx | Effect breakdown into Niagara emitters + materials + performance budget |
Installation
# Copy to your workspace
cp -r unreal-forge-squads/ your-project/.claude/squads/
# Or use alongside UNREAL-FORGE (recommended):
# workspace/
# ├── unreal-forge/ ← Code generation engine
# └── unreal-forge-squads/ ← Expert agent team
Open in Claude Code and start using @agent-name or /UE5-SQUAD: commands.
Technical Specs
| Metric | Value |
|---|---|
| Agents | 8 (1 orchestrator + 7 specialists) |
| Knowledge sources | 9 real UE5 practitioners/educators |
| Anti-patterns detected | 30+ across all domains |
| Task templates | 6 structured workflows |
| Slash commands | 3 |
| Domains covered | Game Design, C++ Architecture, Level Design, VFX, Networking, UI/UX, Performance |
Requirements
- Claude Code — Any plan with agent support
- Unreal Engine 5.x (5.1+)
- UNREAL-FORGE (optional, recommended) — For code generation integration
Credits
Created by @mcsacole
Built on knowledge from the UE5 community's best educators:
- Jesse Schell — The Art of Game Design: A Book of Lenses
- Tracy Fullerton — Game Design Workshop: A Playcentric Approach
- Tom Looman — Professional Game Development in C++ and Unreal Engine
- Alex Forsythe — Unreal Engine C++ Explainer Series
- Alex Galuzin — World of Level Design
- Ashif Ali (CGHOW) — Real-time VFX with Niagara
- Ben Cloward — Shader Development and Technical Art
- Cedric Neukirchen — Multiplayer Network Compendium
- YawLighthouse — UMG-Slate Compendium
License
All rights reserved. Personal and commercial use allowed for the purchaser. Do not redistribute.
UE5 Game Dev Squad v1.0.0 — "Every domain. One team. Zero blind spots."
Reviews (0)
Loading reviews...