PlugWiki

save-systems Skill for Claude Code: Design Crash-Safe Game Saves and Migrations

Guides the agent to design game save/load: what to save, crash-safe writes, schema versions, old-save migration and autosave.

Installs
9.2K
on skills.sh
Stars
6.4K
on GitHub
Files
1
besides SKILL.md
Updated
Oct 2026
last repo commit

save-systems makes the agent follow a 7-step workflow for saving game state. Save plain data, stamp a version number, pick a format, write to a temp file and rename it, load defensively, autosave on safe boundaries, and test loading a save from the previous version.

It triggers when you mention save systems, save/load, save slots, autosave, save file corruption or migrating old saves. It includes four code patterns in GDScript and Python, nine pitfalls and one reference file. It bundles no scripts. It is part of a 77-skill game-dev collection, and the other skills it names are optional.

Good for

  • Indie developers adding save slots and autosave to a game
  • Teams whose old saves break after a patch
  • Developers on Godot, Unity or any other engine, since it is engine-neutral

Install save-systems

Claude Code

  1. 1

    Copy this prompt.

    Install the save-systems skill in Claude Code. Run this command:
    
    claude plugin marketplace add gamedev-skills/awesome-gamedev-agent-skills
    claude plugin install disciplines@awesome-gamedev-agent-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The disciplines plugin is a bundle of 15 cross-engine skills that includes save-systems, and the marketplace entry lists skills only, with no hooks or MCP server. The README command without --skill installs the router plus all 77 skills. Related skills named in SKILL.md (roblox-datastores, godot-resources and others) are optional.

From the project README. Source.

What's in the skill

When it loads

Design save/load for game state — choosing what to serialize, file formats, save slots, atomic crash-safe writes, schema versioning and migration, and autosave. Engine-neutral. Use when the user mentions save system, save/load, game state persistence, save slots, autosave, save file corruption, or migrating old saves to a new version.

Sections in SKILL.md

  1. When to use
  2. Core workflow
  3. Patterns
  4. 1. Serialize state as plain data (not engine objects)
  5. 2. Atomic, crash-safe write (temp + rename)
  6. 3. Versioned load with migration
  7. 4. Save slots + throttled autosave
  8. Pitfalls
  9. References
  10. Related skills

Key facts

Installs on skills.sh
9,165 (Nov 2, 2026)
Last commit
Oct 28, 2026

What it includes

  • Save data such as hp, position, seed and flags, not engine objects

    Objects are rebuilt from data on load; live node references are never serialized.

    Try: “Design a save system for my platformer”

    1. Decide what is authoritative

  • Every save embeds an integer version field

    Called the single most important field for a game you intend to patch.

    2. Versioned schema

  • JSON for readability, binary for size, speed or mild tamper resistance

    Start with JSON.

    3. Pick a format

  • Write a temp file, flush, then rename it over the real save

    A crash leaves the old save or the new one. The Godot example also keeps the previous save as .bak.

    Write · 4. Atomic writes

  • Read version, migrate up, validate, then instantiate; fall back to backup

    A save from a newer build is refused rather than guessed at.

    Files · 5. Defensive load

  • On safe boundaries, throttled, to a separate slot

    The example autosaves at most once a minute and not mid-combat.

    Write · 6. Autosave

  • Save, quit, relaunch, load, and test a save from the previous version

    Confirm by inspection that state matches.

    7. Verify

  • Nine traps, from in-place writes to loading objects from save files

    Includes Godot JSON turning numbers into floats and scripts that can run when objects are loaded from shared saves.

    Pitfalls list

  • Migration chain, backups, format trade-offs, validation checklist, save locations

    references/versioning-and-migration.md also covers where saves live per engine and Steam Cloud setup.

    Read · Reference file

From the official docs

Permissions

Low risk

The skill has the agent write save and load code in your game, and its example code renames and replaces files. Test on copies of real saves before shipping.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It has the agent write file-handling code

    The patterns write temp files and rename them over the real save, keeping a .bak. Test on copies before you trust them with players' saves. github.com

  • It warns about loading objects from saves

    SKILL.md says some Godot load calls can run a script when saves contain objects, and that saves get shared online. Keep saves as plain data. github.com

Technical details
Scopes
  • Edits your game code

Questions

What does save-systems do?

It guides the agent through designing a game save and load system. It covers what to save, crash-safe writes, version fields, migrating old saves and autosave, and it is engine-neutral.

How do I install save-systems?

Use the install box above. In Claude Code you can install the disciplines plugin, which includes this skill among 15, or add only this skill with the skills CLI. The skills CLI needs Node.js 22.20 or later.

Does it work in the Claude app?

Yes, by upload. The repo's install guide lists Claude.ai on Pro, Max, Team and Enterprise plans: turn on code execution and file creation, zip the skill folder and upload it under Customize, Skills.

Does it only work with Godot?

No. The skill says it is engine-neutral. Its examples use GDScript and Python, and for Godot's file API it says to defer to the Godot engine skill.

Do I need the other skills it mentions?

No. It names roblox-datastores, godot-resources, unity-scriptableobjects, procedural-gen and a few genre skills as related. They are separate skills in the same collection.

Is save-systems safe?

It bundles no scripts. It guides the agent to write save and load code in your game, and its examples rename and replace files. Review the code the agent writes, and test with copies of real saves. It also warns that loading objects from shared save files can run scripts.

Information

updated Nov 2, 2026

Folder
skills/disciplines/save-systems

gamedev-skills/awesome-gamedev-agent-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com
  4. github.com · github.com

Updated Nov 2, 2026.