axiom-ios-data

iOS data persistence routing maps your specific storage tasks to the correct backend by evaluating your requirements and directing you to SwiftData, Core Data, GRDB, or SQLite accordingly. It enforces migration safety and documents the decision logic.

Core Data to SwiftData migration is managed by a routing layer that maps your data persistence tasks to the appropriate backend skill and enforces migration safety to prevent data loss during transitions across iOS and macOS apps.

CloudKit synchronization workflows are supported alongside various backends including GRDB and SQLite. The routing skill evaluates your sync requirements and directs the data persistence tasks to the correct backend while managing file storage and data serialization.

A routing layer for iOS data persistence is needed when your app spans multiple backends like SwiftData, Core Data, or CloudKit. It simplifies when and how to use different storage patterns by enforcing migration safety and documenting decision logic.

File storage and data serialization workflows are fully supported. The routing skill guides iOS and macOS data persistence decisions by mapping these specific storage tasks to the correct backend and managing migrations across SwiftData, Core Data, GRDB, and SQLite.

Using a routing skill for SwiftData or Core Data prevents incorrect backend selection by evaluating your data tasks first. It enforces migration safety, documents decision logic, and handles CloudKit sync, ensuring your iOS or macOS storage pattern is appropriate.