Gameplay architecture planning

Convert a feature request into a concrete Unreal Engine design before code or asset work begins. The result should reduce implementation ambiguity without inventing abstractions the project does not need.

This is an architecture and planning skill, not a mandatory gate. If the user asked only for a design, stop at the design. If the user also asked for implementation, perform the design pass briefly and continue within the authorized scope.

When to use this skill

• Brainstorming a gameplay feature, game system, prototype, or project architecture.
• Deciding between Actor, Component, UObject, Subsystem, Game Framework, or asset-based designs.
• Mapping ownership, lifetime, persistence, authority, replication, and communication.
• Defining the C++/Blueprint boundary and designer-facing asset workflow.
• Comparing viable approaches and producing an ordered implementation plan.