managed-component-bridge

What problem does it solve?

This Skill solves the challenge of coordinating ECS-driven logic with Unity’s managed world (GameObjects, MonoBehaviours, and Unity UI elements) when you must hold managed references on an entity.

Core Features & Use Cases

• Managed reference boundary: Stores managed objects on ECS entities using class-based IComponentData to bridge hybrid initialization safely.
• One-time initialization pattern: Recommends a self-disabling initialization system so the managed component exists only to set up the bridge once.
• Performance and GC guardrails: Provides a GC cost model and concrete anti-patterns to avoid Burst access and hot-path usage.

Quick Start

Use managed-component-bridge when an ECS system needs to control a GameObject or Unity UI element during one-time hybrid initialization, and ensure your initialization system self-disables after wiring the references.