Agent skill · software engineering · affaan-m
swift-actor-persistence
Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design. Use when persisting data in Swift and a data race or thread-safety problem needs designing out.
Why this skill is useful
Provides a specific implementation pattern for thread-safe data persistence in Swift using actors, which the AI may not generate reliably on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Swift Actors for Thread-Safe Persistence Patterns for building thread-safe data persistence layers using Swift actors. Combines in-memory caching with file-backed storage, leveraging the actor model to eliminate data races at compile time. When to Activate Building a data persistence layer in Swift 5.5+ Need thread-safe access to shared mutable state Want to eliminate manual synchronization (locks, DispatchQueues) Building offline-first apps with local storage Core Pattern Actor-Based Repository The actor model guarantees serialized access — no data races, enforced by the compiler. Usage All calls are automatically async due to actor isolation: Combining with @Observable ViewModel Key Design Decisions Decision Rationale ---------- ----------- Actor (not class + lock) Compiler-enforced thread safety, no manual synchronization In-memory cache + file persistence Fast reads from cache, durable writes to disk Synchronous init loading Avoids async initialization complexity Dictionary keyed by ID O(1) lookups by identifier Generic over Codable & Identifiable Reusable across any model type Atomic file writes (.atomic) Prevents partial writes on crash Best Practices Use Sendable types for all data crossing actor boundaries Keep the actor's public API minimal — only expose domain operations, not persistence details Use .atomic writes to prevent data corruption if the app crashes mid-write Load synchronously in init — async initializers add complexity with minimal benefit for local files Combine with @Observable ViewModels for reactive UI updates Anti-Patterns to Avoid Using DispatchQueue or NSLock instead of actors for new Swift concurrency code Exposing the internal cache dictionary to external callers Making the file URL configurable without validation Forgetting that all actor method calls are await — callers must handle async context Using nonisolated to bypass actor isolation (defeats the purpose) When to Use Local data storage in iOS/macOS apps (user data, settings, cac …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/swift-actor-persistence--ef7f14