Axiom Swiftdata Migration Diag

What it does

This skill, Axiom Swiftdata Migration Diag, helps diagnose and resolve issues encountered during migrations from Axiom to SwiftData in frontend projects. It focuses on identifying common configuration errors that lead to migration failures, such as missing models, incorrect relationship inverses, or untested migration paths. The tool emphasizes that these problems are almost always due to configuration mistakes, not bugs within the SwiftData framework itself.

When to use it

This skill is valuable in the following situations:

• You're experiencing app crashes after a schema change.
• You encounter errors like "Expected only Arrays for Relationships," "incompatible model," or "Failed to fulfill faulting."
• Your migration works in the simulator but fails on real devices.
• Data disappears or relationships break after a migration.
• You need to ensure your SwiftData migrations are robust and reliable before releasing your application.

Key capabilities

• Error Identification: Helps pinpoint the type of migration error based on crash messages (e.g., relationship inverse missing, schema version mismatch).
• Schema Version Verification: Guides users in verifying that the schema versions defined in the MigrationPlan match those used within the application.
• Model Inclusion Check: Ensures all necessary models are included in the VersionedSchema.
• Relationship Inverse Validation: Assists in checking and correcting relationship inverse declarations.

Example prompts

While this skill doesn't directly respond to prompts, it provides a checklist of steps to follow when encountering migration issues. Examples of what you might think about while using the tool:

• "I’m seeing an 'Expected only Arrays' error; how do I troubleshoot it?"
• "My app crashes on real devices but works in the simulator – what could be wrong?"
• “How can I verify that all my models are included in the SwiftData schema?”

Tips & gotchas

• Real Device Testing is Mandatory: Always test migrations on a real device with actual data before shipping your app. Simulators hide critical schema mismatch issues due to their database reset behavior.
• Focus on Configuration: Remember that migration failures are almost always caused by configuration errors, not SwiftData bugs.
• Follow the Checklist: The skill provides a specific checklist of steps (identify error type, check schema version, verify models, validate inverses) – follow these in order for effective troubleshooting.