agentsclimarketplace

Ue5 architecture

Skill teixasalone/UnrealEngine5-Skills/skills/ue5-architecture

Provide reusable workflows for Unreal Engine 5.6/5.7 to simplify Blueprint, C++, UI, PCG, replication, debugging, and performance tasks.

Install
npx -y skills add teixasalone/UnrealEngine5-Skills --skill ue5-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 16 stars16 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

UE5.6/UE5.7 architecture planning and module boundary design for Unreal projects. Use when requests involve module layout, Build.cs dependencies, reflection exposure strategy, Public/Private API boundaries, naming conventions, and preventing circular dependencies.

SKILL.md

1.7 KB, as published. Nobody here has run it

Quick Start

  • Collect current module list, *.Build.cs, and major gameplay/UI systems.
  • Propose one target module graph before writing code.
  • Output module responsibilities and ownership in a table.

Workflow

  • Identify runtime, editor, UI, networking, and data modules from current codebase.
  • Define Public API for each module as minimal headers and Blueprint surface.
  • Define Private implementation boundaries and include rules.
  • Define PublicDependencyModuleNames and PrivateDependencyModuleNames per module.
  • Report risks: circular includes, over-exposed reflection types, and cross-layer references.

Constraints

  • Keep UCLASS/USTRUCT/UENUM only where reflection is required.
  • Prefer forward declarations in headers; include concrete headers in .cpp.
  • Do not move types across modules without listing migration impact.
  • Keep naming aligned with Unreal conventions (U, A, F, E prefixes).

Failure Handling

  • If ownership of a class is ambiguous, place it in runtime module first and log a TODO to split after usage mapping.
  • If dependency graph becomes cyclic, extract shared contracts into a thin common module.
  • If Build.cs dependencies are uncertain, choose minimal set and verify compile paths immediately.

Escalation

  • Escalate when a refactor requires asset redirectors, class renames, or package path migration.
  • Escalate when module split changes public Blueprint class paths used by existing content.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.