From ios
Migrates iOS code between frameworks (UIKit↔SwiftUI), data layers (CoreData↔SwiftData), and Swift versions (5→6) with configurable strategies.
How this command is triggered — by the user, by Claude, or both
Slash command
/ios:migrate [source] [target] [--strategy incremental|complete]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /ios:migrate - iOS Migration Migrate `$ARGUMENTS` between frameworks, patterns, and Swift versions. ## Arguments | Flag | Values | Default | Description | |------|--------|---------|-------------| | `--strategy` | incremental\|complete\|hybrid | incremental | Migration strategy | | `--validate` | - | - | Validate migration | | `--backup` | - | - | Create backup before migration | | `--adr` | - | - | Create Architecture Decision Record | ## Migration Paths | From | To | Strategy | |------|-----|----------| | UIKit | SwiftUI | incremental recommended | | CoreData | SwiftData | complete...
Migrate $ARGUMENTS between frameworks, patterns, and Swift versions.
| Flag | Values | Default | Description |
|---|---|---|---|
--strategy | incremental|complete|hybrid | incremental | Migration strategy |
--validate | - | - | Validate migration |
--backup | - | - | Create backup before migration |
--adr | - | - | Create Architecture Decision Record |
| From | To | Strategy |
|---|---|---|
| UIKit | SwiftUI | incremental recommended |
| CoreData | SwiftData | complete recommended |
| ObservableObject | @Observable | complete |
| Completion handlers | async/await | incremental |
| Swift 5.x | Swift 6 | validate first |
| MVC | MVVM/TCA | incremental |
| Strategy | Use When |
|---|---|
incremental | Large codebase, risk mitigation |
complete | Small scope, full replacement |
hybrid | Mixed usage during transition |
1. analysis:
- Assess current implementation
- Identify dependencies
- Estimate effort
2. planning:
- Create migration plan
- Define milestones
- Set up feature flags if needed
3. execution:
- Migrate in phases
- Maintain backward compatibility
- Update tests
4. validation:
- Run full test suite
- Performance comparison
- User acceptance
/ios:migrate uikit swiftui --strategy incremental
/ios:migrate coredata swiftdata --backup
/ios:migrate swift5 swift6 --validate
/ios:migrate observableobject observable --strategy complete
# Migration: [Source] → [Target]
## Strategy: incremental | complete | hybrid
## Files Affected: X files
## Changes: Before → After
## Validation: Tests | Performance | Compatibility
## ADR: [If --adr]
npx claudepluginhub carolanelfbv/ios-development-agents --plugin ios/migrateAlias for /portaljs-migrate that will be removed next minor release. Invoke /portaljs-migrate instead.
/migratePlans and executes incremental framework or library migrations: audits dependencies, analyzes breaking changes, creates ordered plan, executes module-by-module, verifies with tests and performance checks.
/migrateAnalyzes legacy ETL (stored procedures, SSIS, Informatica) and produces modern dbt models, PySpark jobs, Airflow DAGs, migration mappings, and validation queries.
/migrateMigrate ADVPL procedural .prw code to TLPP object-oriented .tlpp code with classes, namespaces, and modern patterns. Analyzes structure, shows detailed plan requiring approval, then generates files and optional wrapper.
/migrateMigrate Nuxt UI from v2/v3 to v4: auto-detects version, fixes breaking changes in components/configs/composables, updates deps, runs checks. Use --dry-run to preview or --from v3.
/migrateMigrates project from Task Master MCP to native markdown-based task tracking: verifies artifacts, ports pending tasks to /docs/wip Markdown files, cleans up files, updates configs and docs.