ue-gameplay-architecture-planning

Plans Unreal Engine gameplay system architectures with ownership, replication, and implementation maps.

55|5|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/kevinpbuckley/unreal-engine-skills --skill ue-gameplay-architecture-planning-kevinpbuckley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ue-gameplay-architecture-planning
Source: https://github.com/kevinpbuckley/unreal-engine-skills/tree/main/skills/core/ue-gameplay-architecture-planning
Command: npx skills add https://github.com/kevinpbuckley/unreal-engine-skills --skill ue-gameplay-architecture-planning-kevinpbuckley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing a new Unreal Engine gameplay feature without a clear architecture leads to misplaced state, broken replication, and costly refactors. This Skill turns an ambiguous feature idea into a concrete Unreal-native design before any code or asset work begins. ## Core Features & Use Cases - Architecture Decision Guidance: Chooses among Actor, Component, UObject, Subsystem, Game Framework classes, and data assets using decision matrices grounded in UE 5.8 engine source. - Structured Design Maps: Produces responsibility/lifetime maps, object/component trees, communication and replication flows, data models, and explicit C++/Blueprint boundaries. - Ordered Implementation Plans: Sequences work as vertical slices with verification checkpoints, risks, and open decisions. - Use Case: When asked to add a multiplayer inventory system, the Skill maps authoritative state to PlayerState components, defines Server RPC validation flows, separates Data Asset definitions from runtime state, and outputs a phased task list for an implementation agent. ## Quick Start Ask the agent to design the architecture for a new gameplay feature, such as "plan a multiplayer stamina system for my UE 5.8 project," and it will produce the full design maps and implementation plan.

Frequently Asked Questions about ue-gameplay-architecture-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a gameplay system architecture in Unreal Engine?

Break the feature into responsibilities like authoritative rules, replicated state, and presentation, then assign each one owner such as GameMode, PlayerState, or a Subsystem. This Skill guides that process and outputs decision maps plus an ordered implementation plan.

Should I use an Actor, Component, UObject, or Subsystem in Unreal Engine?

Use an Actor for world presence and independent replication, an ActorComponent for behavior owned by one Actor, a UObject for lightweight structured data, and a Subsystem for services matching Engine, GameInstance, World, or LocalPlayer lifetimes. The included decision matrices walk through this selection.

Where should player state live in Unreal multiplayer games?

Durable per-player state that survives death belongs on PlayerState, not the Pawn, since Pawns are destroyed and repossessed. GameMode holds server-only rules and never exists on clients, while GameState holds replicated match-wide state.

Does this skill support Unreal Engine 5.8?

Yes, it targets UE 5.8 APIs and terminology, with citations into the 5.8 engine source headers. It flags recommendations that depend on experimental plugins or behavior differing across UE 5.x versions.

When should I not use architecture planning for Unreal features?

Skip it for localized bug fixes or mechanical edits where the architecture is already settled. It is designed for new features, system brainstorming, and cross-cutting decisions involving networking, persistence, or the C++/Blueprint boundary.