SwiftData (Before)
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-sqlitedata-migrationExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-sqlitedata-migration from charleswiltgen/axiom and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate axiom-sqlitedata-migration. Access via /axiom-sqlitedata-migration in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
767
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
767
stars
┌─────────────────────────────────────────────────────────┐
│ Should I switch from SwiftData to SQLiteData? │
├─────────────────────────────────────────────────────────┤
│ │
│ Performance problems with 10k+ records? │
│ YES → SQLiteData (10-50x faster for large datasets) │
│ │
│ Need CloudKit record SHARING (not just sync)? │
│ YES → SQLiteData (SwiftData cannot share records) │
│ │
│ Complex queries across multiple tables? │
│ YES → SQLiteData + raw GRDB when needed │
│ │
│ Need Sendable models for Swift 6 concurrency? │
│ YES → SQLiteData (value types, not classes) │
│ │
│ Testing @Model classes is painful? │
│ YES → SQLiteData (pure structs, easy to mock) │
│ │
│ Happy with SwiftData for simple CRUD? │
│ YES → Stay with SwiftData (simpler for basic apps) │
│ │
└─────────────────────────────────────────────────────────┘
| SwiftData | SQLiteData |
|---|---|
@Model class Item |
@Table nonisolated struct Item |
@Attribute(.unique) |
@Column(primaryKey: true) or SQL UNIQUE |
@Relationship var tags: [Tag] |
var tagIDs: [Tag.ID] + join query |
@Query var items: [Item] |
@FetchAll var items: [Item] |
@Query(sort: \.title) |
@FetchAll(Item.order(by: \.title)) |
@Query(filter: #Predicate { $0.isActive }) |
@FetchAll(Item.where(\.isActive)) |
@Environment(\.modelContext) |
@Dependency(\.defaultDatabase) |
context.insert(item) |
Item.insert { Item.Draft(...) }.execute(db) |
context.delete(item) |
Item.find(id).delete().execute(db) |
try context.save() |
Automatic in database.write { } block |
ModelContainer(for:) |
prepareDependencies { $0.defaultDatabase = } |
SwiftData (Before)
import SwiftData
@Model
class Task {
var id: UUID
var title: String
var isCompleted: Bool
var project: Project?
init(title: String) {
self.id = UUID()
self.title = title
self.isCompleted = false
}
}
struct TaskListView: View {
@Environment(\.modelContext) private var context
@Query(sort: \.title) private var tasks: [Task]
var body: some View {
List(tasks) { task in
Text(task.title)
}
}
func addTask(_ title: String) {
let task = Task(title: title)
context.insert(task)
}
func deleteTask(_ task: Task) {
context.delete(task)
}
}
SQLiteData (After)
import SQLiteData
@Table
nonisolated struct Task: Identifiable {
let id: UUID
var title = ""
var isCompleted = false
var projectID: Project.ID?
}
struct TaskListView: View {
@Dependency(\.defaultDatabase) var database
@FetchAll(Task.order(by: \.title)) var tasks
var body: some View {
List(tasks) { task in
Text(task.title)
}
}
func addTask(_ title: String) {
try database.write { db in
try Task.insert {
Task.Draft(title: title)
}
.execute(db)
}
}
func deleteTask(_ task: Task) {
try database.write { db in
try Task.find(task.id).delete().execute(db)
}
}
}
Key differences:
class → struct with nonisolated@Model → @Table@Query → @FetchAll@Environment(\.modelContext) → @Dependency(\.defaultDatabase)database.write { } block.Draft type for inserts@Relationship → Explicit foreign key + joinSwiftData supports CloudKit sync but NOT sharing. SQLiteData is the only Apple-native option for record sharing.
// 1. Setup SyncEngine with sharing
prepareDependencies {
$0.defaultDatabase = try! appDatabase()
$0.defaultSyncEngine = try SyncEngine(
for: $0.defaultDatabase,
tables: Task.self, Project.self
)
}
// 2. Share a record
@Dependency(\.defaultSyncEngine) var syncEngine
@State var sharedRecord: SharedRecord?
func shareProject(_ project: Project) async throws {
sharedRecord = try await syncEngine.share(record: project) { share in
share[CKShare.SystemFieldKey.title] = "Join my project!"
}
}
// 3. Present native sharing UI
.sheet(item: $sharedRecord) { record in
CloudSharingView(sharedRecord: record)
}
Sharing enables: Collaborative lists, shared workspaces, family sharing, team features.
| Operation | SwiftData | SQLiteData | Improvement |
|---|---|---|---|
| Insert 50k records | ~4 minutes | ~45 seconds | 5x |
| Query 10k with predicate | ~2 seconds | ~50ms | 40x |
| Memory (10k objects) | ~80MB | ~20MB | 4x smaller |
| Cold launch (large DB) | ~3 seconds | ~200ms | 15x |
Benchmarks approximate, vary by device and data shape.
Critical: Schema migration alone loses all user data. You must export from SwiftData and import into SQLiteData.
// 1. Read all records from SwiftData's backing store
func migrateExistingData(from modelContext: ModelContext, to database: any DatabaseWriter) throws {
// Fetch all SwiftData records
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
649mattpocock/skills
Productivitysame categorypremortem
214parcadei/continuous-claude-v3
Productivitysame categorydeslop
159cursor/plugins
Productivitysame categorytravel-planner
136ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
131pproenca/dot-skills
Productivitysame categorywrite-a-prd
128mattpocock/skills
Productivitysame categoryReviews
4.8★★★★★71 reviews- HHana Rao★★★★★Dec 28, 2024
Registry listing for axiom-sqlitedata-migration matched our evaluation — installs cleanly and behaves as described in the markdown.
- JJames Ndlovu★★★★★Dec 28, 2024
Keeps context tight: axiom-sqlitedata-migration is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNeel Mensah★★★★★Dec 20, 2024
Useful defaults in axiom-sqlitedata-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- IIra Wang★★★★★Dec 20, 2024
axiom-sqlitedata-migration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- HHana Gupta★★★★★Dec 16, 2024
Registry listing for axiom-sqlitedata-migration matched our evaluation — installs cleanly and behaves as described in the markdown.
- JJames Gonzalez★★★★★Dec 12, 2024
We added axiom-sqlitedata-migration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- JJames Ramirez★★★★★Dec 4, 2024
axiom-sqlitedata-migration reduced setup friction for our internal harness; good balance of opinion and flexibility.
- YYash Thakker★★★★★Nov 23, 2024
We added axiom-sqlitedata-migration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- JJames Abbas★★★★★Nov 23, 2024
I recommend axiom-sqlitedata-migration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- AArya Iyer★★★★★Nov 19, 2024
Useful defaults in axiom-sqlitedata-migration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 71
1 / 8Discussion
Comments — not star reviews- No comments yet — start the thread.
axiom-sqlitedata-migration — AI agent skill | explainx.ai | explainx.ai