Game Development State Change Notification

Use when a cross-engine gameplay task needs a Layer 1 foundation for change callbacks, invalidation signals, observer updates, or diff-vs-snapshot semantics, and the agent must define or review a reusable state-change notification model with explicit change boundaries, timing rules, payload shape, batching policy, and invalidation semantics.

LoogacyStudio Updated 0 repo stars

File contents

LoogacyStudio/skills commit 779a7a2f82

Frequently asked questions

npx get-skill add loogacystudio/game-development-state-change-notification