Save Systems is an engine-neutral skill for the save file itself: its format, writes, versioning, slots and location. It uses Godot and Python code to show how to serialize ids and flags, write through a temp file with a backup, and migrate old saves one version at a time.
The agent finds the existing save code first, adds an integer version, loads defensively and runs a round-trip and corruption test before asking you to quit and relaunch the game.
What You Get
- A capture and apply pattern that saves data and rebuilds nodes from it on load
- An atomic write with a temp file and a .bak that the loader falls back to
- A versioned loader that refuses newer saves and migrates older ones step by step
- Separate manual slots and a throttled autosave file
- A headless round-trip and corruption test that prints a pass or fail line
- A gotchas list on JSON number types, loading objects from saves and save locations
Common Use Cases
- Adding save, load and a continue button to a new game
- Fixing saves that corrupt after a crash or power loss
- Keeping old saves working after a patch changes the data shape
- Setting up autosave at checkpoints without overwriting manual slots
What Makes It Unique
It treats the save as a long-lived contract. Every save carries a version from the first release, migrations are pure functions kept forever, and the loader falls back to a backup. It also records Godot specifics that bite in practice, such as JSON loading every number as a float and Windows rename deleting the target first.
Under The Hood
The skill is a SKILL.md with one reference file on versioning and migration. The agent searches your project for existing save code and shipped saves, edits game code and writes a small test script under a tools folder. It runs the engine headless from the command line to execute the round-trip test, which writes and deletes temporary save files in the user data folder. It does not fetch web pages or call outside services.