Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement saving for [game] using [engine and target platform]. Persist [explicit progress facts] at [checkpoint policy]. Keep temporary effects and interface-only state outside the save unless the requirements explicitly need them.
Define stable object identities, save format recognition, user ownership, and handling for supported older saves, missing data, and damaged records. Use appropriate platform storage. Design write failure so it does not casually destroy the last usable copy. Explain any separate cloud-conflict policy.
Verify reaching a known state, quitting the process, launching again, and reconstructing the intended result. Check missing-save and controlled failure scenarios. Report save versions, platforms checked, and progress intentionally excluded.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original save template grounded in persistence/reconstruction and user-data paths. Compatibility and failure protection are implementation obligations that need real fixtures.