What is code-organization-pattern?

A set of rules for arranging C++ source files with named sections, grouped imports, and explanatory comments. C++ is a programming language commonly used for game engines and other performance-sensitive software.

Use it when creating or reorganizing C++ files, especially when grouping imports and code by responsibility.

It gives files a predictable structure, making large files easier to read and maintain.

code-organization-pattern — Cursor rule by Stramp

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/stramp/lost-mines-phandelver/code-organization-pattern

Clone the repo

git clone --depth 1 https://github.com/Stramp/Lost-Mines-Phandelver

Made for: Cursor.

Per session 1,773 This file is loaded in full into every session.

When invoked 1,773 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.01773	$0.01773
Opus 5	$0.00886	$0.00886
Sonnet 5	$0.00355	$0.00355
Haiku 4.5	$0.00177	$0.00177

Measured yesterday against content hash 230e8a840d94, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-organization-pattern scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/code-organization-pattern.mdc · 410 lines

How it starts

The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Organization Pattern

🎯 Objective

ALWAYS organize C++ files following a consistent pattern with:

Clear section comments
Regions to group related code
Includes grouped by category
Logical organization by responsibility
Explanatory comments in important functions

📋 Mandatory Structure

1. File Header

ALWAYS start with:

// Copyright Epic Games, Inc. All Rights Reserved.

#pragma once

// ============================================================================
// Includes
// ============================================================================
#pragma region Includes

// Project includes - [categoria]
#include "..."

// Engine includes
#include "..."

#pragma endregion Includes

2. Organization with Regions

ALWAYS use #pragma region to group related code:

// ============================================================================
// [Section Name]
// ============================================================================
#pragma region [Section Name]

// Related code here...

#pragma endregion [Section Name]

3. Section Comments

ALWAYS use section comments with separators:

// ============================================================================
// Section Name
// ============================================================================

Separator pattern:

Use === to create visual line
Consistent spacing
Titles in PascalCase or descriptive

📁 Organization by File Type

.cpp Files (Implementation)

Mandatory structure:

// Copyright Epic Games, Inc. All Rights Reserved.

// ============================================================================
// Includes
// ============================================================================
#pragma region Includes

#include "[Header].h"

// Project includes - [categoria 1]
#include "..."

// Project includes - [categoria 2]
#include "..."

// Engine includes
#include "..."

#if WITH_EDITOR
#include "..."
#endif

#pragma endregion Includes

// ============================================================================
// [Seção Principal 1]
// ============================================================================
#pragma region [Seção Principal 1]

/**
 * Comentário explicativo da função.
 * Explica o "porquê" e o "como" quando necessário.
 */
void Function1()
{
    // Implementação
}

#pragma endregion [Seção Principal 1]

// ============================================================================
// [Seção Principal 2]
// ============================================================================
#pragma region [Seção Principal 2]

// Mais código...

#pragma endregion [Seção Principal 2]

Read the full file on GitHub · 410 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 410 lines · 1,773 tokens per session scan A 230e8a840d94

Subscribe to this mod's changes

code-organization-pattern is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 1,773 tokens to every session, about $0.0089 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Game development

architecture

Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.

andvolodko/html5-game-editor · 49 tokens

code-organization-pattern