Ue Navigating Engine Source logo

Ue Navigating Engine Source

Community
kevinpbuckley
ue-navigating-engine-source

Locate, read, and cite exact Unreal Engine APIs in the on-disk engine source instead of guessing. Use when you need a real function signature, class hierarchy, UPROPERTY/UFUNCTION specifier, module name, or include path; when verifying that an API exists in UE 5.8; when resolving "which module do I add to Build.cs?"; or when an API changed between engine versions. Covers the full source tree layout (Runtime/Editor/ Developer/Plugins), the Public/Private/Classes folder convention, UHT-generated files, naming prefixes as navigation hints, IWYU include rules, and repeatable search patterns for finding any class, function, or type from first principles.

Overview

Publisherkevinpbuckley
Repositoryunreal-engine-skills
Skill nameue-navigating-engine-source
Stars
89
Forks
9
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by kevinpbuckley on GitHub. Read the source before you install it.

Installation

Install the Ue Navigating Engine Source AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/kevinpbuckley/unreal-engine-skills/tree/master/skills/core/ue-navigating-engine-source
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/kevinpbuckley/unreal-engine-skills.git /tmp/unreal-engine-skills
mkdir -p .claude/skills
cp -r /tmp/unreal-engine-skills/skills/core/ue-navigating-engine-source .claude/skills/ue-navigating-engine-source
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ue Navigating Engine Source in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ue Navigating Engine Source on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ue Navigating Engine Source is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Navigating the Unreal Engine source

The engine's own C++ source is the ground truth for every signature, specifier, and include path. Before asserting any API detail, verify it in the source. Memory is often a version or two stale.

When to use this skill

  • You need the exact signature of a UFUNCTION/UPROPERTY/virtual override, or its specifiers and meta=(...) clauses.
  • You are unsure whether an API exists, was renamed, or moved in 5.8.
  • You need the correct #include path or the module name to add to *.Build.cs.
  • You want to see how Epic structures a class before writing similar code.
  • You are resolving a build error ("unresolved external", "identifier not found") caused by a missing #include or missing Build.cs dependency.

Source tree on this machine

VersionRootNotes
5.8 (primary)E:\Program Files\Epic Games\UE_5.8\EngineBinary install; ships full C++ source
5.7E:\Program Files\Epic Games\UE_5.7\EngineBinary install; previous release for comparison
5.5.1E:\Repo\Git\UE_5_5_1_Fresh\UnrealEngine\EngineFull source build

Default to 5.8. Use the others only to compare signatures across versions.

Confirm the exact version any time: E:\Program Files\Epic Games\UE_5.8\Engine\Build\Build.version → MajorVersion 5, MinorVersion 8, PatchVersion 1.

Source tree organization

Engine\Source\ has five top-level subdirectories:

FolderPurposeIn shipping builds?
Runtime\Gameplay, rendering, audio, net, core — the most-needed codeYes
Editor\Editor tools (UnrealEd, Kismet, BlueprintGraph, LevelEditor)No
Developer\Build tooling, profiling helpers, automationNo
Programs\Standalone executables (UBT, UnrealLightmass, AutomationTool)No
ThirdParty\Vendored external sourceVaries

Plugins (often where newer and optional systems live) are under Engine\Plugins\, organized by category: AI\, Animation\, EnhancedInput\, FX\ (Niagara), Runtime\ (GameplayAbilities, CommonUI, …), Experimental\, and more.

Rule: an API under Source\Editor\ or behind #if WITH_EDITOR is unavailable in a packaged game. Verify the path before depending on it.

Module structure (Public / Private / Classes)

Every module is a folder under Source\<Tier>\<ModuleName>\ containing:

<ModuleName>/
  Classes/              — reflected types (UCLASS/USTRUCT/UENUM headers)
  Public/               — public non-reflected headers
  Private/              — private headers and all *.cpp files
  <ModuleName>.Build.cs — declares the module; lists dependencies

The Engine module exemplifies all three roots. Its Classes\ tree has category subfolders grounded in the 5.8 tree:

  • Runtime\Engine\Classes\GameFramework\ — Actor.h, Character.h, GameModeBase.h, PlayerController.h, Pawn.h, GameStateBase.h, PlayerState.h, SpringArmComponent.h, SaveGame.h
  • Runtime\Engine\Classes\Components\ — ActorComponent.h, SceneComponent.h, PrimitiveComponent.h, StaticMeshComponent.h, SkeletalMeshComponent.h, CapsuleComponent.h, AudioComponent.h, SplineComponent.h, TimelineComponent.h
  • Runtime\Engine\Classes\Engine\ — World.h:931, EngineTypes.h, AssetManager.h, Canvas.h
  • Runtime\Engine\Classes\Kismet\ — GameplayStatics.h, BlueprintFunctionLibrary.h, KismetMathLibrary.h, KismetSystemLibrary.h
  • Runtime\Engine\Classes\Animation\ — AnimInstance.h, AnimMontage.h
  • Runtime\Engine\Classes\Camera\ — CameraComponent.h, PlayerCameraManager.h

Other key Runtime modules:

  • Runtime\Core\Public\ — CoreMinimal.h, Containers\Array.h, Containers\Map.h, Math\Vector.h, Delegates\
  • Runtime\CoreUObject\Public\UObject\Object.h — UObject:98, CreateDefaultSubobject:129
  • Runtime\GameplayTags\Classes\GameplayTagContainer.h — FGameplayTag:41, FGameplayTagContainer:247
  • Runtime\AIModule\Classes\ — AIController.h, BehaviorTree\, EnvironmentQuery\, Perception\
  • Runtime\UMG\Public\ — UUserWidget, UWidgetComponent, widget bindings

Naming prefixes as navigation hints

UHT enforces naming conventions — knowing the prefix tells you what type you have and roughly where to look:

PrefixKindExamples
AActor (AActor subclass)ACharacter, AGameModeBase:47, APlayerController
UUObject (non-actor)UActorComponent, UStaticMeshComponent, UWorld:931
FNon-UObject struct/classFVector, FHitResult, FGameplayTag:41
EEnumEEndPlayReason, ECollisionChannel
TTemplate classTArray, TObjectPtr, TSubclassOf, TWeakObjectPtr
IInterfaceIGameplayTaskOwnerInterface
GGlobal variableGWorld, GEngine

Prefixes are enforced by UHT — a mismatch is a compile error.

The *_API macro tells you the module

Every exported symbol carries a <MODULE>_API macro. The module name is the macro prefix, lowercased:

MacroModule (Build.cs name)
ENGINE_API"Engine"
CORE_API"Core"
COREUOBJECT_API"CoreUObject"
AIMODULE_API"AIModule"
GAMEPLAYABILITIES_API"GameplayAbilities"
GAMEPLAYTAGS_API"GameplayTags"
UMG_API"UMG"
SLATECORE_API"SlateCore"

Confirm by finding <ModuleName>.Build.cs under the source folder.

Repeatable "find X" workflow

1. Find a class header

Glob for **/<ClassName>.h under the source root, then confirm with Grep:

Glob("**/Character.h", path="E:/Program Files/Epic Games/UE_5.8/Engine/Source")
→ Runtime\Engine\Classes\GameFramework\Character.h

Grep("class ACharacter", path="...Character.h")
→ line 338: class ACharacter : public APawn

2. Find a function signature

Grep within the known file; read a ±10-line window — do not read the whole file:

Grep("virtual.*BeginPlay", path="...Actor.h", output_mode="content")
→ line 2125: ENGINE_API virtual void BeginPlay();

Read(path="...Actor.h", offset=2121, limit=15)  // read only the relevant range

3. Resolve module → include → Build.cs

  1. Find the header: Glob or Grep for the type across Engine\Source\.
  2. Identify the module: the source folder directly under Source\<Tier>\ that contains the found file. Confirm by locating <Module>.Build.cs there.
  3. Write the #include: relative to the module's Public\/Classes\ root, e.g. #include "GameFramework/Actor.h" (not the absolute path).
  4. Add to Build.cs: PublicDependencyModuleNames if the type appears in your public headers; PrivateDependencyModuleNames otherwise.

4. Plugin APIs

Plugin headers follow the same pattern under Engine\Plugins\. Also confirm:

  • The plugin is enabled in .uproject (the Plugins array).
  • The module name matches <Module>.Build.cs inside Source\<Module>\.

Example: UAbilitySystemComponent → Engine\Plugins\Runtime\GameplayAbilities\Source\GameplayAbilities\Public\AbilitySystemComponent.h → module "GameplayAbilities".

Reading reflection specifiers

UPROPERTY and UFUNCTION lines directly above a member ARE the API contract. Read them when you need to reproduce or override behavior:

Grep("ReplicatedUsing", path="...Actor.h", output_mode="content")
→ line 351: UPROPERTY(ReplicatedUsing=OnRep_ReplicateMovement, Category=Replication, EditDefaultsOnly)

The meta=(...) clause carries editor/Blueprint semantics — copy it faithfully when implementing similar APIs:

line 364: UPROPERTY(Interp, EditAnywhere, Category=Rendering, BlueprintReadOnly, Replicated,
              meta=(AllowPrivateAccess="true", DisplayName="Actor Hidden In Game", ...))

UCLASS(BlueprintType, Blueprintable, config=Engine, meta=(ShortTooltip="..."), MinimalAPI) (Actor.h:281) is the canonical example of a full class specifier line.

The *.generated.h contract

Every reflected header (UCLASS, USTRUCT, UENUM) must:

  1. Include its <ClassName>.generated.h as the last #include.
  2. Have GENERATED_BODY() as the first statement in the class body.

Never edit *.generated.h — it is produced by Unreal Header Tool (UHT) before the C++ compiler runs and regenerated on every build. Generated files live under the module's Intermediate\ folder, not in Source\.

Verified examples (UE 5.8)

All paths relative to E:\Program Files\Epic Games\UE_5.8\Engine\Source\:

AActor (Runtime\Engine\Classes\GameFramework\Actor.h):

  • :281 UCLASS(BlueprintType, Blueprintable, config=Engine, meta=(ShortTooltip="..."), MinimalAPI)
  • :2125 ENGINE_API virtual void BeginPlay();
  • :2132 ENGINE_API virtual void EndPlay(const EEndPlayReason::Type EndPlayReason);
  • :3060 ENGINE_API virtual void Tick(float DeltaSeconds);
  • :3124 ENGINE_API virtual void PreInitializeComponents();
  • :3127 ENGINE_API virtual void PostInitializeComponents();
  • :3445 virtual void OnConstruction(const FTransform& Transform) {}
  • :3569 ENGINE_API virtual void Destroyed();

ACharacter (Runtime\Engine\Classes\GameFramework\Character.h:338)

AGameModeBase (Runtime\Engine\Classes\GameFramework\GameModeBase.h:47)

UWorld (Runtime\Engine\Classes\Engine\World.h:931)

UObject (Runtime\CoreUObject\Public\UObject\Object.h:98), CreateDefaultSubobject:129

FGameplayTag (Runtime\GameplayTags\Classes\GameplayTagContainer.h:41), FGameplayTagContainer:247

(Line numbers drift between patch releases — re-Grep to confirm, but paths and class/function names are stable.)

Gotchas

  • Editor vs Runtime: code under Source\Editor\ or in WITH_EDITOR blocks is stripped from packaged games. Check before depending on it.
  • Plugin gating: a plugin API exists only when the plugin is enabled in the .uproject. If missing, the symbol will not compile.
  • Version skew: if a signature differs from memory, the source wins. Note the difference when producing code or skill content.
  • Never read a whole large header: Actor.h is ~4,500 lines; World.h exceeds 5,000. Grep first; then Read a focused offset+limit window.
  • *.generated.h last, GENERATED_BODY() first: violating either rule produces cryptic UHT or compiler errors.
  • IWYU: include only specific headers you use — not Engine.h or UnrealEd.h. The compiler will warn on monolithic includes.

References & source material

Engine source (UE 5.8, under E:\Program Files\Epic Games\UE_5.8\Engine\):

  • Version file: Build\Build.version (5.8.1, changelist 56057345).
  • Primary source root: Engine\Source\ → Runtime\, Editor\, Developer\, Programs\, ThirdParty\.
  • Plugin root: Engine\Plugins\ → AI\, Animation\, EnhancedInput\, FX\, Runtime\, Experimental\, and more.
  • Runtime\Engine\Classes\GameFramework\Actor.h — canonical example of a large reflected class with all lifecycle hooks.
  • Runtime\Core\Public\CoreMinimal.h — the ubiquitous minimal include set.
  • Runtime\CoreUObject\Public\UObject\Object.h — UObject base class.

Official docs (UE 5.8, fetched and confirmed):

Cross-reference sibling skills:

  • ue-module-and-build-system — full *.Build.cs / *.Target.cs authoring guide.
  • ue-cpp-fundamentals — UCLASS/USTRUCT/UENUM/UPROPERTY/UFUNCTION in depth.
  • ue-coding-standards — Epic naming conventions and prefix rules.

Deep-dive references in this skill:

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ue Navigating Engine Source AI skill do?

Locate, read, and cite exact Unreal Engine APIs in the on-disk engine source instead of guessing. Use when you need a real function signature, class hierarchy, UPROPERTY/UFUNCTION specifier, module name, or include path; when verifying that an API exists in UE 5.8; when resolving "which module do I add to Build.cs?"; or when an API changed between engine versions. Covers the full source tree layout (Runtime/Editor/ Developer/Plugins), the Public/Private/Classes folder convention, UHT-generated files, naming prefixes as navigation hints, IWYU include rules, and repeatable search patterns for...

Why use Ue Navigating Engine Source on TypingMind?

Because you install it once and use it with any model. Ue Navigating Engine Source is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ue Navigating Engine Source in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/kevinpbuckley/unreal-engine-skills/tree/master/skills/core/ue-navigating-engine-source. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ue Navigating Engine Source?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ue Navigating Engine Source?

As many as you like. As long as a model supports skills, you can use Ue Navigating Engine Source with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ue Navigating Engine Source AI skill free?

It is published on GitHub by kevinpbuckley. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇