Individual skill
scene-organization
Use when designing scene tree structure — composition vs inheritance, when to split scenes, node hierarchy patterns
skills/scene-organization/SKILL.md
Source commit d7b26cdb5fae14d4ef7b713c5bf259395e75c3c6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 948
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-skills Repository topic
- claude-code Repository topic
- copilot Repository topic
- csharp Repository topic
- game-development Repository topic
- gamedev Repository topic
- gdscript Repository topic
- godot Repository topic
- godot-4 Repository topic
- godot-engine Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Scene Organization
A guide for structuring Godot 4.3+ scene trees: when to split, when to compose, and how nodes should communicate.
> **Related skills:** **component-system** for composition patterns, **event-bus** for decoupled communication, **godot-brainstorming** for scene tree planning, **2d-essentials** for TileMapLayer and CanvasLayer organization.
---
## 1. Core Principle
Scenes are building blocks. Each scene encapsulates exactly one concept — a player, an enemy, a health bar, a weapon. A scene should be understandable in isolation, reusable without modification, and replaceable without breaking its neighbors.
> One scene = one responsibility. If you struggle to name a scene in two words or fewer, it is probably doing too much.
