domains / families / software-engineering / core-data

core-data

separate

Build, review, or improve Core Data persistence in apps that have not adopted SwiftData. Use when working with NSManagedObject subclasses, NSFetchedResultsController for list-driven UI, NSBatchInsertRequest / NSBatchDeleteRequest / NSBatchUpdateRequest for bulk operations, NSPersistentHistoryChangeRequest for persistent history tracking and multi-target sync, NSStagedMigrationManager for staged schema migrations (iOS 17+), NSCompositeAttributeDescription for composite attributes (iOS 17+), or when integrating Core Data threading with Swift Concurrency. For Core Data + SwiftData coexistence or migration, see the swiftdata skill instead.

When to use

• Core Data persistence
• NSManagedObject subclasses
• NSFetchedResultsController for list-driven UI
• NSBatchInsertRequest / NSBatchDeleteRequest / NSBatchUpdateRequest
• NSPersistentHistoryChangeRequest for persistent history tracking
• NSStagedMigrationManager for staged schema migrations
• NSCompositeAttributeDescription for composite attributes
• Core Data threading with Swift Concurrency

When not to use

• Core Data + SwiftData coexistence
• SwiftData migration

Skill page

Source