What problem does it solve? Changing GameState fields, renaming content ids, or bumping SCHEMA_VERSION in the kami-kakushi codebase can silently orphan old player saves, break the fixtures gate, or corrupt stored data. This Skill provides the ordered schema-bump recipe, migration test patterns, and hazard list needed to evolve the save format without losing player progress. ## Core Features & Use Cases - Schema-Bump Recipe: Step-by-step checklists for the three schema-growth rungs (additive field, rename/restructure, world reboot), including hydration defaults, identity migration steps, and the version-history doc line. - Migration Test Patterns: Guidance for hand-built inline fixtures, registry-derived assertions, MemoryBackend wiring tests, and idempotency-safe migration functions. - Hazard & Incident Knowledge: Documents known traps such as positional log keys, orphaned content ids, the renderLogLine import trap, and the missing old-save e2e gate. - Use Case: You add a new asksHeard field to GameState. The Skill walks you through adding the hydration default with numAdditive, bumping SCHEMA_VERSION, adding an identity migration step, writing the hydration test, and regenerating fixtures in the same commit. ## Quick Start Ask the assistant to walk you through adding a new field to GameState and bumping SCHEMA_VERSION using the kami-save-and-schema recipe.
