Naming Conventions

Overview

The namespace scan showed the following style in use:

• Lightforge.* for technical runtime namespaces
• internal experimental namespaces for non-public work

Rules

• Use stable names for public assets and inspector-facing content
• Keep internal experimental work clearly marked
• Do not rename things casually once they are referenced by scenes or prefabs

Media Suggestions

• Screenshot: Namespace examples in the code editor.
• Screenshot: Asset naming in the Project window.
• GIF: Refactor preview before and after.
• Video: Naming rules for a new module.
• Diagram: Namespace hierarchy by runtime area.