Imported from andres00567/Unreal-MCP-Extension (Skills/ue-project-orientation/SKILL.md). Install upstream with npx skills add andres00567/Unreal-MCP-Extension --skill ue-project-orientation. Copyright stays with the author.

UE Project Orientation

Outcome

Build an evidence-based project map before proposing architecture or edits.

Inspect

1. Read the .uproject, enabled project plugins, target files, and module Build.cs files.
2. Identify runtime, editor, developer, and test modules and their dependency direction.
3. Find analogous classes/assets with bounded source and Asset Registry searches.
4. Identify the project’s default maps, game mode, major subsystems, naming conventions, and existing automation tests.
5. Distinguish native code, Blueprint-owned behavior, configuration, and generated output.

Do not infer asset contents from filenames or invent project conventions. Report what was inspected and flag binary assets that require Unreal-native inspection.

Before editing

Choose the existing extension point that owns the behavior. Avoid introducing a parallel subsystem, hard-coded content root, or new plugin until the current ownership model is understood.