scene-lifecycle-composition-workflow

What problem does it solve?

This Skill addresses the fragility of scene composition in game development by providing a structured workflow to ensure scene hierarchies remain stable, lifecycle responsibilities are clear, and signal connections are resilient to refactoring and instancing changes.

Core Features & Use Cases

• Explicit Ownership: Defines clear boundaries for scene subsystems and their lifecycle management.
• Signal Stability: Ensures signals connected at composition boundaries remain functional even after subtree moves or instancing updates.
• Refactoring Safety: Provides a method to rehearse and validate hierarchy changes before committing, preventing broken node paths and signal flows.
• Use Case: When refactoring a complex UI system where different parts are managed by separate scenes, this Skill helps ensure that signals like "button_pressed" or "data_updated" continue to function correctly after moving UI elements or changing how sub-scenes are instantiated.

Quick Start

Use the scene-lifecycle-composition-workflow skill to define scene roots and ownership boundaries for each subsystem.