axiom-core-data-diag

Diagnose Core Data crashes and apply safe migration patterns.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/tuliopc23/flying-dutchman-app --skill axiom-core-data-diag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-core-data-diag
Source: https://github.com/tuliopc23/flying-dutchman-app/tree/main/.claude/skills/axiom-core-data-diag
Command: npx skills add https://github.com/tuliopc23/flying-dutchman-app --skill axiom-core-data-diag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers systematically diagnose and resolve complex issues within Apple's Core Data framework, preventing data loss and app crashes related to schema migrations, concurrency, and performance.

Core Features & Use Cases

  • Crash Diagnosis: Identifies the root cause of Core Data crashes, such as "Unresolvable fault" (schema mismatch) or "different thread" (concurrency errors).
  • Migration Safety: Provides patterns for safe and reliable schema migrations, ensuring data integrity across app versions.
  • Performance Optimization: Offers strategies to detect and fix N+1 query problems and other performance bottlenecks.
  • SwiftData/Core Data Bridging: Guides on managing mixed SwiftData and Core Data environments.
  • Use Case: A production app is crashing after a recent Core Data schema update. This Skill guides the developer through checking store vs. model versions, identifying the exact mismatch, and applying the correct migration pattern to fix it without data loss.

Quick Start

Run the mandatory first steps to diagnose the Core Data issue by checking schema versions, thread confinement, and N+1 queries.

Frequently Asked Questions about axiom-core-data-diag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the mandatory first steps to debug a Core Data production crash?

The mandatory first steps to debug a Core Data production crash involve checking schema versions, verifying thread confinement, and identifying N+1 queries. This Skill systematically guides you through these initial diagnostic checks.

How do I fix Core Data concurrency errors when accessing managed objects on different threads?

Core Data concurrency errors occur when managed objects are accessed from different threads without proper thread confinement. This Skill diagnoses these violations and guides you through the mandatory first steps to resolve the concurrency issue.

What is the best way to detect and resolve N+1 query performance problems in Core Data?

To resolve N+1 query performance problems in Core Data, you must detect the bottlenecks causing excessive fetch requests. This Skill offers systematic strategies to identify these issues and optimize query performance.

Can I use SwiftData and Core Data together in the same iOS application?

Yes, you can bridge SwiftData and Core Data in the same iOS application. This Skill provides guidance on managing mixed environments, helping you navigate concurrency and data integrity across both frameworks.

How do I safely perform Core Data schema migrations without losing user data?

Safely performing Core Data schema migrations without data loss requires checking store versus model versions and applying reliable migration patterns. This Skill provides systematic diagnostics to ensure data integrity across app versions.

What are the mandatory first steps to debug a Core Data production crash?

The mandatory first steps to debug a Core Data production crash involve checking schema versions, verifying thread confinement, and identifying N+1 queries. This Skill systematically guides you through these initial diagnostic checks.