SwiftData schema migrations move your data safely when models change. Core principle SwiftData's willMigrate sees only OLD models, didMigrate sees only NEW models—you can never access both simultaneously. This limitation shapes all migration strategies.
Fetches axiom-swiftdata-migration from charleswiltgen/axiom and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/axiom-swiftdata-migration
Restart Cursor to activate axiom-swiftdata-migration. Access via /axiom-swiftdata-migration in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
SwiftData schema migrations move your data safely when models change. Core principle SwiftData's willMigrate sees only OLD models, didMigrate sees only NEW models—you can never access both simultaneously. This limitation shapes all migration strategies.
Requires iOS 17+, Swift 5.9+
Target iOS 26+ (features like propertiesToFetch)
When Custom Migrations Are Required
Lightweight Migrations (Automatic)
SwiftData can migrate automatically for:
✅ Adding new optional properties
✅ Adding new required properties with default values
You cannot directly transform data from old type to new type in a single migration stage. Example:
// ❌ IMPOSSIBLE - you can't do this in one stagewillMigrate:{ context inlet oldNotes =try context.fetch(FetchDescriptor<SchemaV1.Note>())for oldNote in oldNotes {let newNote =SchemaV2.Note()// ❌ Doesn't exist yet! newNote.content = oldNote.contentAsAttributedString()}}
Solution Use two-stage migration pattern (covered below).
Core Patterns
Pattern 1: Basic VersionedSchema Setup
Every distinct schema version must be defined as a VersionedSchema.
importSwiftDataenumNotesSchemaV1:VersionedSchema{staticvar versionIdentifier =Schema.Version(1,0,0)staticvar models:[any PersistentModel.Type]{[Note.self,Folder.self,Tag.self]// ALL models, even if unchanged}@ModelfinalclassNote{@Attribute(.unique)var id:Stringvar title:Stringvar content:String// Original typevar createdAt:Date@Relationship(deleteRule:.nullify, inverse:\Folder.notes)var folder:Folder?@Relationship(deleteRule:.nullify, inverse:\Tag.notes)var tags:[Tag]=[]init(id:String, title:String, content:String, createdAt:Date){self.id = id
self.title = title
self.content = content
self.createdAt = createdAt
}}@ModelfinalclassFolder{@Attribute(.unique)var id:Stringvar name:String@Relationship(deleteRule:.cascade)var notes:[Note]=[]init(id:String, name:String){self.id = id
self.name = name
}}@ModelfinalclassTag{@Attribute(.unique)var id:Stringvar name:String@Relationship(deleteRule:.nullify)var notes:[Note]=[]init(id:String, name:String){self.id = id
self.name = name
}}}
Key patterns
Complete snapshot All models included, even unchanged ones
Semantic versioning Use Schema.Version(major, minor, patch)
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
