swiftuimigrator-screens
SwiftUI Migrator Screens
Overview
Use this skill for the repeated screen-by-screen migration loop after the app shell and startup path are stable.
Core principle: move one screen and one feature slice at a time, and compare SwiftUI behavior against the original UIKit implementation before changing architecture.
When to Use
- A root or secondary
ViewControllerneeds a SwiftUI replacement - The app shell is stable enough to begin screen conversion
- Features need to move incrementally from UIKit into SwiftUI
- Navigation must be rewritten with SwiftUI patterns
- A complex UIKit component may need a temporary
UIViewRepresentablebridge
Scope
- Screen selection and naming
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-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.
1swiftuimigrator-data-migration
Use when SwiftUI app startup still needs initialization, migration, loading-state orchestration, AppInitializer work, or SplashScreen progress handling.
1