ue-cpp-style

Enforce Unreal Engine C++ coding standards for naming, formatting, and modern practice.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill ue-cpp-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ue-cpp-style
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/ue-cpp-style
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill ue-cpp-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unreal Engine C++ projects often suffer from inconsistent naming, formatting, and outdated practices that hinder readability, maintainability, and collaboration. This guide provides a single, authoritative set of rules to standardize coding across teams and projects.

Core Features & Use Cases

  • Naming conventions, formatting rules, ownership semantics, and modern C++ practices tailored for Unreal Engine.
  • Guidelines for UE-specific patterns such as reflection macros, UPROPERTY pointers, and macro usage that improve safety and readability.
  • Real-world use cases demonstrating how to apply the rules during development and code reviews.

Quick Start

Read this guide before writing or reviewing UE C++ code to ensure compliance with the modern UE style rules.

Frequently Asked Questions about ue-cpp-style

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

FAQPage Schema
What are the Unreal Engine C++ coding standards for naming and formatting?

Unreal Engine C++ coding standards enforce consistent naming, formatting, and modern practices by specifying clang-format style, type prefixes, UPROPERTY pointers, and safe ownership semantics for readable code.

How do I enforce modern C++ practices in Unreal Engine during code reviews?

You enforce modern C++ practices in Unreal Engine by applying rules for reflection macros, UPROPERTY pointer ownership, and IWYU guidance during code reviews to ensure safe, consistent code.

When do I need to use UPROPERTY pointers and reflection macros in UE C++?

You need UPROPERTY pointers and reflection macros in UE C++ when defining UObject-derived types to enable garbage collection, reflection, and safe ownership semantics across typical Unreal workflows.

Does this UE C++ style guide work with clang-format for automated formatting?

Yes, this UE C++ style guide specifies a clang-format style to automate formatting, ensuring consistent file headers, using directives, and modern practice across Unreal Engine development teams.

What is the best way to standardize Unreal Engine C++ naming conventions across a team?

The best way to standardize UE C++ naming conventions is adopting an authoritative style guide enforcing type prefixes, file headers, and macro usage rules to align development and code reviews.

Why does my Unreal Engine C++ code need IWYU guidance and safe pointer semantics?

Unreal Engine C++ code needs IWYU guidance and safe pointer semantics to prevent outdated practices, ensure correct ownership, and maintain readability, maintainability, and collaboration across projects.