structural-change-cost-model

What problem does it solve?

This Skill removes guesswork from ECS state transitions by providing a canonical decision model for when to mutate values, toggle enableable components, or perform structural add/remove operations.

Core Features & Use Cases

• Decision Tree for ECS Transitions: Select value mutation, enableable component toggles, or structural changes based on change frequency and semantic intent.
• Frequency Rule of Thumb: Applies consistent thresholds (e.g., > 1/sec per entity) to choose the lowest-cost approach that still preserves clarity.
• Performance Risk Guidance: Highlights runtime risks like chunk migration spikes and archetype churn, so you can avoid expensive patterns at scale.
• Architecture Guidance: Recommends using structural boundaries to create meaningful archetypes (e.g., “Dead” entities excluded from queries) to reduce query-time complexity.

Quick Start

Apply the frequency rule to your ECS state change and choose value mutation, enableable toggle, or structural add/remove accordingly.