What problem does it solve? Stateful libraries and long-running batch operations lose progress or corrupt data when processes crash, restart, or run concurrently. This Skill provides standardized patterns for persisting state reliably across restarts and system failures. ## Core Features & Use Cases - Atomic JSON Persistence: Write state to temporary files and rename atomically to prevent corruption on crash. - File Locking & Concurrency: Use fcntl-based exclusive locks to protect state files from concurrent modification. - Crash Recovery & Versioning: Design resumable state with checkpoints, progress tracking, and schema migration paths. - Use Case: When building a batch processing tool that handles dozens of features, use the BatchStateManager pattern to track completed and failed items, then resume from the last checkpoint after an interruption with a --resume flag. ## Quick Start Ask the agent to implement state persistence for a batch processing library using atomic writes and crash recovery so it can resume after interruptions.