Game Development Entity Reference Boundary

Use when a cross-engine gameplay task needs a Layer 1 foundation for entity identity, stale references, payload safety, or handle-versus-pointer trade-offs, and the agent must define or review a reusable entity-reference boundary with explicit identity rules, lookup strategy, lifetime policy, payload safety, and debugging expectations.

LoogacyStudio Updated 0 repo stars

File contents

LoogacyStudio/skills commit 20cea93db7

Frequently asked questions

npx get-skill add loogacystudio/game-development-entity-reference-boundary