navigating-engine-source

Locate and verify exact Unreal Engine APIs, signatures, and module paths in on-disk engine source.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/ziyarduc/Baran-bk-game --skill navigating-engine-source-ziyarduc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: navigating-engine-source
Source: https://github.com/ziyarduc/Baran-bk-game/tree/main/.agents/skills/navigating-engine-source
Command: npx skills add https://github.com/ziyarduc/Baran-bk-game --skill navigating-engine-source-ziyarduc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Unreal Engine API details memorized from docs or older versions are often stale or wrong, causing compile errors, missing includes, and unresolved externals. This Skill grounds every API claim in the actual on-disk engine source so signatures, specifiers, include paths, and Build.cs module names are verified instead of guessed. ## Core Features & Use Cases - Exact API Verification: Find real UFUNCTION/UPROPERTY signatures, specifiers, meta clauses, and class hierarchies directly in UE 5.8 source headers. - Module and Include Resolution: Map any type to its module via the *_API macro and Public/Private/Classes layout, producing the correct #include path and Build.cs dependency entry. - Repeatable Search Workflows: Six Grep/Glob/Read-based playbooks for locating classes, functions, specifiers, plugin APIs, and cross-version signature differences without reading multi-thousand-line headers. - Use Case: You need to override BeginPlay in a custom actor and are unsure of its exact signature in UE 5.8. The Skill greps Actor.h, confirms ENGINE_API virtual void BeginPlay();, and tells you the Engine module is already the right dependency. ## Quick Start Ask the agent to verify the exact signature and required Build.cs module for a specific Unreal Engine class or function using the installed UE 5.8 engine source.

Frequently Asked Questions about navigating-engine-source

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

FAQPage Schema
How do I find the exact signature of a UFUNCTION in Unreal Engine source?▼

Grep for the function name in the expected header under Engine\Source, then read a focused 10-15 line window around the match. Never read entire large headers like Actor.h or World.h, which exceed 4,000 lines.

How do I know which module to add to Build.cs for an Unreal Engine class?▼

Find the header containing the class, then identify the source folder directly under Source\Runtime or Source\Editor that contains it. The *_API macro on the symbol also encodes the module name, such as ENGINE_API mapping to the Engine module.

Can I use Editor module APIs in a packaged Unreal Engine game?▼

No. Code under Source\Editor or inside #if WITH_EDITOR blocks is stripped from packaged builds. Verify the header path before depending on it, or wrap usage in WITH_EDITOR guards.

Why does my Unreal Engine class fail to compile with UHT errors?▼

Common causes are a missing or misplaced *.generated.h include, which must be the last include, or GENERATED_BODY() not being the first statement in the class body. Naming prefix violations, such as a UCLASS not starting with A or U, also fail UHT.

How do I check if an Unreal Engine API changed between versions?▼

Grep the same symbol in each installed engine root, such as UE 5.5.1, 5.7, and 5.8 source trees, then diff the results. Line numbers drift between patch releases, so always re-grep rather than trusting memorized locations.

How do I use a plugin API like GameplayAbilities in my Unreal project?▼

Locate the header under Engine\Plugins, confirm the module via its Build.cs file, add the module name to your Build.cs dependencies, and ensure the plugin is enabled in your .uproject file's Plugins array.