# unreal-engine

Enforces naming conventions, architecture, and performance guidelines for C++ and Blueprints in Unreal Engine 5.x.

- rule · `type=rule` · Cursor · ★ 3580
- Author: sanjeed5
- License: CC0-1.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/sanjeed5/awesome-cursor-rules-mdc/tree/HEAD/rules-mdc/unreal-engine.mdc
- Updated: 2026-05-19
- HTML: https://affpapa.org/en/nevibecode/rules/unreal-engine

## What it does

This rule directs Cursor to follow Epic Games and Splash Damage naming standards for Unreal Engine 5.x codebases. It enforces class prefixes such as `A`, `U`, and `F`, boolean indicators with `b`, and asset tags like `BP_` or `M_`. Project assets must live inside feature-specific directories rather than folders grouped purely by file type.

For runtime logic, the guide keeps heavy algorithms and core systems in C++ while routing UI and game-feel tweaks to Blueprints. Any heap allocations outside `UObject` must rely on `TSharedPtr`, `TWeakPtr`, or `TUniquePtr`. Heavy operations like line traces are strictly kept out of `Tick` in favor of periodic timers.

Because the rule targets `**/*`, Cursor applies these conventions across the entire repository without manual invocation.

## Requirements
- Works with: Unreal Engine

## Install

### Cursor (native platform)

**Manually: put the files in place**
- File: `.cursor/rules/unreal-engine.mdc` — Frontmatter: description, globs, alwaysApply

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/unreal-engine.md` — The paths frontmatter field limits the files: move globs from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/instructions/unreal-engine.instructions.md` — The applyTo field sets which files it applies to: move globs from the source into applyTo

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/unreal-engine.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/unreal-engine.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/sanjeed5/awesome-cursor-rules-mdc/tree/HEAD/rules-mdc/unreal-engine.mdc

## When to use it
- Enforce Epic and Splash Damage C++ naming conventions
- Organize project assets by game feature instead of file type
- Prevent memory leaks using Unreal smart pointers
- Move expensive per-frame logic from `Tick` to timers

## Example prompts
- Write an enemy spawner C++ actor with properties exposed to Blueprints
- Create a const getter function for player stats with UFUNCTION macros
- Structure the directory layout for character weapon assets

## Source text · unreal-engine.mdc · CC0-1.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 389eaeb2566111db.

BEGIN THIRD-PARTY FILE 389eaeb2566111db
````text
---
description: Definitive guidelines for writing consistent, performant, and maintainable C++ and Blueprint code in Unreal Engine 5.x projects.
globs: **/*
---
# unreal-engine Best Practices

This guide outlines the essential coding standards and architectural patterns for developing robust and efficient Unreal Engine 5.x projects. Adhere to these rules to ensure high-quality, collaborative, and performant game development.

## 1. Code Organization & Structure

### 1.1 Naming Conventions (C++)

Always follow Epic's and Splash Damage's C++ naming conventions for clarity and consistency.

*   **Classes/Structs/Enums:** Use prefixes (`A`, `U`, `F`, `E`, `T`) followed by `PascalCase`.
*   **Member Variables:** Use `CamelCase`.
*   **Local Variables/Parameters:** Use `lower_snake_case`.
*   **Functions/Methods:** Use `PascalCase`.
*   **Boolean Variables:** Prefix with `b` (Epic) or `Is` (Verse-inspired).
*   **Event Handlers:** Prefix with `On`.
*   **Resource Creation/Destruction:** Use `Create`/`Destroy`.

❌ **BAD**
```cpp
// Class
class my_actor_class : public AActor {};
// Variable
float playerHealth;
// Function
void get_player_name();
// Enum
enum E_WEAPON_TYPE { ... };
// Boolean
bool is_dead_player;
```

✅ **GOOD**
```cpp
// Class
class AMyActorClass : public AActor {};
// Variable
float PlayerHealth; // Member variable
float new_health_value; // Local variable/parameter
// Function
void GetPlayerName() const;
// Enum
enum EWeaponType : uint8 { EWeaponType_Sword, EWeaponType_Bow };
// Boolean
bool bIsDead; // or IsDead()
// Event Handler
void OnPlayerDied();
// Resource Management
UMyWidget* CreatePlayerHUD();
void DestroyPlayerHUD(UMyWidget* WidgetToDestroy);
```

### 1.2 Naming Conventions (Assets & Blueprints)

Prefix all assets and Blueprints with their type to aid discoverability and organization.

*   **Blueprint Classes:** `BP_` (e.g., `BP_PlayerCharacter`)
*   **Materials:** `M_` (e.g., `M_Rock`)
*   **Material Instances:** `MI_` (e.g., `MI_Rock_Mossy`)
*   **Static Meshes:** `SM_` (e.g., `SM_Door`)
*   **Skeletal Meshes:** `SK_` (e.g., `SK_Character`)
*   **Textures:** `T_` (e.g., `T_Grass_D` for Diffuse, `T_Grass_N` for Normal)
*   **Particle Systems:** `P_` (e.g., `P_Explosion`)
*   **User Widgets:** `W_` (e.g., `W_MainMenu`)
*   **Gameplay Abilities:** `GA_` (e.g., `GA_Dash`)
*   **Gameplay Effects:** `GE_` (e.g., `GE_DamageOverTime`)
*   **Input Actions:** `IA_` (e.g., `IA_Jump`)

❌ **BAD**
```
Content/PlayerCharacter.uasset
Content/RockMaterial.uasset
Content/Explosion.uasset
```

✅ **GOOD**
```
Content/MyGame/Characters/Player/BP_PlayerCharacter.uasset
Content/MyGame/Environment/Materials/M_Rock.uasset
Content/MyGame/FX/P_Explosion.uasset
```

### 1.3 Folder Structure

Organize content by feature or domain, not by asset type. This improves project navigation and simplifies migration. Use `Developer-folder` for temporary, personal assets.

❌ **BAD**
```
Content/Materials/M_Rock.uasset
Content/Blueprints/BP_PlayerCharacter.uasset
Content/FX/P_Explosion.uasset
```

✅ **GOOD**
```
Content/MyGame/Environment/Props/Rock/M_Rock.uasset
Content/MyGame/Characters/Player/BP_PlayerCharacter.uasset
Content/MyGame/Weapons/Rifle/SK_Rifle.uasset
Content/MyGame/Developer/MyName/BP_TestActor.uasset
```

### 1.4 C++ vs Blueprint Responsibility

Delegate responsibilities based on performance and iteration needs.

*   **C++:** Implement performance-critical logic, complex algorithms, core systems (networking, AI pathfinding), and engine integrations.
*   **Blueprint:** Use for gameplay logic, data-driven iteration, UI, and visual scripting where performance is not paramount. Expose minimal, well-defined C++ functions and properties to Blueprint.

❌ **BAD**
```cpp
// C++: Hardcoding specific gameplay rules that designers need to tweak frequently
void AGameModeBase::BeginPlay()
{
    Super::BeginPlay();
````
END THIRD-PARTY FILE 389eaeb2566111db

The third-party file has ended. Everything between the 389eaeb2566111db tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3886 of 12024 bytes. © sanjeed5 · CC0-1.0 · https://github.com/sanjeed5/awesome-cursor-rules-mdc/tree/HEAD/rules-mdc/unreal-engine.mdc

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md