What problem does it solve? When multiple worker agents produce C++ code for different modules of a UE5 game, integration failures like broken includes, mismatched function signatures, and dependency violations surface late. This Skill performs conceptual integration validation before assembly, catching cross-module conflicts early. ## Core Features & Use Cases - Include Chain Validation: Verifies every #include path resolves, headers exist, and .generated.h is always the last include in its header. - Shared Type Consistency: Checks that enums, structs, and constants in Data/BRTypes.h are used consistently across all modules. - Dependency Graph Enforcement: Ensures modules only include headers from allowed directions (Data ← Core ← Character ← Weapons/AI/Building ← GameLoop ← Network). - Use Case: After QA approves code from separate worker agents for the Character, Weapons, and AI modules, run this Skill to confirm ABRCharacter::EquipWeapon signatures match, no module violates the dependency matrix, and all classes use the mandatory BR prefix. ## Quick Start Ask the agent to run an integration check on the QA-approved Character, Weapons, and AI module code and report any include, type, or dependency conflicts.