godot-scene-architecture
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGodot Scene Architecture
Godot 场景架构
Purpose
目的
Structure scenes, nodes, autoloads, and resources so Godot projects remain scalable and understandable.
合理组织场景、节点、autoloads和资源,让Godot项目保持可扩展性与可读性。
Use When
适用场景
- scene nesting is growing
- autoloads are becoming global dumping grounds
- node ownership is unclear
- 场景嵌套层级不断增加
- autoloads 逐渐变成全局“垃圾场”
- 节点归属关系不清晰
Inputs
输入信息
- feature behavior
- scene tree patterns
- autoload list
- resource and signal usage
- 功能特性行为逻辑
- 场景树模式
- autoload 列表
- 资源与信号使用情况
Process
实施流程
- define what belongs in scenes, autoloads, and reusable resources
- keep node hierarchy and responsibility understandable
- avoid brittle hardcoded node path dependencies
- control signal ownership and scene lifetime carefully
- document scene composition patterns for the team
- 明确场景、autoloads和可复用资源的职责划分
- 确保节点层级结构与职责清晰易懂
- 避免脆弱的硬编码节点路径依赖
- 谨慎管控信号归属与场景生命周期
- 为团队编写场景组合模式文档
Outputs
输出成果
- scene architecture notes
- autoload boundary rules
- signal and ownership guidance
- anti-pattern warnings
- 场景架构说明文档
- autoload 边界规则
- 信号与归属关系指导规范
- 反模式警示内容
Quality Bar
质量标准
- respects scene-tree ownership, autoload boundaries, and resource behavior
- keeps scripts, signals, and resources understandable at scale
- supports export reliability and content iteration without hidden coupling
- 遵循场景树归属规则、autoload 边界与资源行为特性
- 确保脚本、信号和资源在项目规模扩大后仍保持可读性
- 支持可靠导出与内容迭代,无隐藏耦合问题
Common Failure Modes
常见失败模式
- autoloads becoming global dumping grounds
- signal webs with no ownership
- shared resources causing accidental state leakage
- autoloads 沦为全局“垃圾场”
- 无明确归属的信号网络
- 共享资源导致意外状态泄露
Related Agents
关联Agent
- godot-reviewer
- gameplay-programmer
- ui-programmer
- godot-reviewer
- gameplay-programmer
- ui-programmer
Related Commands
关联命令
- godot-review
- godot-scene-audit
- tech-design
- godot-review
- godot-scene-audit
- tech-design
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.
- 确保本技能与相关规则层及当前项目文档保持一致。
- 如果引擎特定约束对工作流程产生重大影响,请转交至匹配的引擎技能或引擎专属审核人员处理。