swiftuimigrator-data-migration
SwiftUI Migrator Data Migration
Overview
Use this skill after the SwiftUI app shell exists but before screen-by-screen migration starts. It moves initialization, data migration, and heavy startup work into the SwiftUI startup flow safely.
Core principle: complete startup stabilization before screen migration, so feature work does not carry hidden app-lifecycle risk.
When to Use
AppDelegatestill owns initialization or migration logic- Startup work needs an
AppInitializer SplashScreenshould display loading or migration progress- Core Data to SwiftData migration is part of the move to SwiftUI
- Startup work is slow, failure-prone, or currently hard to observe
Scope
- Inventory startup responsibilities currently in UIKit lifecycle code
More from 2sem/swiftui-migrator-skill
swiftuimigrator
Use when planning or coordinating an incremental UIKit-to-SwiftUI migration and you need to determine which migration stage or specialized subskill should run next.
1swiftuimigrator-admob
Use when the SwiftUI migration is already stable and the remaining work is Google AdMob integration, SwiftUIAdManager setup, ad-unit migration, or native ad UI migration.
1swiftuimigrator-cleanup
Use when the SwiftUI migration is already verified and the remaining work is deleting legacy UIKit files, removing old entry logic, and doing final cleanup safely.
1swiftuimigrator-screens
Use when converting UIKit ViewControllers into SwiftUI screens, migrating features incrementally, rewiring navigation, or bridging complex UIKit views with UIViewRepresentable.
1swiftuimigrator-project-setup
Use when a UIKit-to-SwiftUI migration still needs project-level setup such as Tuist updates, App.swift creation, SplashScreen setup, or entry-point transition from AppDelegate.
1