save-system

Persist and restore Unity game state with JSON serialization and versioned migrations.

3|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/OmerZeyveli/kinglet-unity --skill save-system-omerzeyveli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-system
Source: https://github.com/OmerZeyveli/kinglet-unity/tree/main/.claude/skills/gameplay/save-system
Command: npx skills add https://github.com/OmerZeyveli/kinglet-unity --skill save-system-omerzeyveli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured patterns for persisting and restoring Unity game state reliably across sessions, scenes, save slots, and future format changes.

Core Features & Use Cases

  • Saveable state architecture: Implement stable ISaveable contracts for components that capture and restore their own data.
  • Save management: Coordinate JSON serialization, save slots, autosaves, atomic file writes, metadata, deletion, and scene restoration.
  • Persistence guidance: Distinguish gameplay saves from PlayerPrefs settings, support per-scene persistence, prepare for cloud synchronization, and migrate versioned save data.
  • Use Case: When building an inventory, health, quest, or destroyed-object system, use these patterns to save its state with stable keys and restore it after loading the appropriate scene.

Quick Start

Use the save-system skill to design and implement a versioned Unity save manager with save slots, autosave support, scene persistence, and ISaveable components for the player inventory and health.

Frequently Asked Questions about save-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save and restore Unity game state across scene transitions?

To save Unity game state across scene transitions, use scene-aware restoration patterns with stable save keys and JSON serialization to capture and reload destroyed objects, inventory, and health data.

What's the best way to structure a Unity save system with multiple save slots?

A reliable Unity save system coordinates save slots, autosave checkpoints, and metadata using atomic file writes and JSON serialization to prevent data corruption during the save process.

Should I use PlayerPrefs for saving Unity gameplay data?

PlayerPrefs should be restricted to non-gameplay settings only, while gameplay data like inventory, health, and quests require structured JSON serialization with atomic file writes for reliable persistence.

How do I handle backward compatibility when migrating Unity save data formats?

Backward-compatible save migrations in Unity require versioned data structures that apply migration steps sequentially, allowing older save files to upgrade safely to new formats without losing player progress.

Can I prepare my Unity save system for cloud saves?

Cloud save preparation in Unity involves structuring save data with stable keys, JSON serialization, and atomic writes so serialized payloads remain sync-ready for remote storage synchronization.

How do ISaveable contracts work for persisting Unity component data?

ISaveable contracts let Unity components capture and restore their own data independently using stable save keys, enabling a save manager to serialize player inventory, health, and quest state without tight coupling.