unreal-cpp-standards
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseUnreal CPP Standards
Unreal C++ 标准
Purpose
目的
Apply C++ standards that fit Unreal lifecycle, reflection, modules, and gameplay framework concerns.
应用适配Unreal生命周期、反射、模块及游戏玩法框架要求的C++标准。
Use When
适用场景
- writing or reviewing Unreal C++
- C++ and Blueprint boundaries are unclear
- module quality needs consistency
- 编写或评审Unreal C++代码时
- C++与Blueprint边界不清晰时
- 需要统一模块质量时
Inputs
输入信息
- feature scope
- existing modules
- reflection and tooling needs
- performance constraints
- 功能范围
- 现有模块
- 反射与工具需求
- 性能约束
Process
实施流程
- keep ownership and responsibility explicit across engine classes
- minimize leaking implementation details into public reflected APIs
- document lifecycle-sensitive behavior such as possession, replication, and initialization
- keep modules and dependencies intentional
- review performance-heavy Tick and allocation patterns
- 明确引擎类之间的所有权与职责
- 尽量避免将实现细节泄露到公开的反射API中
- 记录对生命周期敏感的行为,比如占有、复制与初始化
- 合理规划模块与依赖关系
- 评审性能密集型的Tick函数与内存分配模式
Outputs
输出成果
- C++ guideline application
- API boundary notes
- review findings
- refactor candidates
- C++准则应用方案
- API边界说明
- 评审结果
- 重构候选项
Quality Bar
质量标准
- respects Unreal framework ownership, packaging, and content pipeline realities
- keeps C++, Blueprints, plugins, and content boundaries intentional
- makes replication, map setup, and packaging risk explicit
- 遵循Unreal框架的所有权、打包及内容管线实际情况
- 明确划分C++、Blueprints、插件与内容之间的边界
- 明确复制、地图设置及打包过程中的风险
Common Failure Modes
常见失败模式
- Blueprint graph sprawl hiding ownership
- using Tick where event-driven logic is clearer
- packaging or plugin state changing without documentation
- Blueprint图结构混乱,隐藏所有权关系
- 在事件驱动逻辑更清晰的场景下使用Tick
- 打包或插件状态变更未做文档记录
Related Agents
相关Agent
- unreal-reviewer
- code-reviewer
- gameplay-programmer
- unreal-reviewer
- code-reviewer
- gameplay-programmer
Related Commands
相关命令
- unreal-review
- refactor-clean
- verify
- unreal-review
- refactor-clean
- verify
Notes
注意事项
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
- 保持本skill与相关规则层及当前项目文档一致。
- 如果引擎特定约束对工作流程产生重大影响,转交至匹配的引擎skill或引擎特定评审人员。