name: crash-instrumentation description: Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies. triggers:

• "breadcrumb strategy"
• "capture crashes"
• "crash context"
• "crash reporting"
• "debug crashes"
• "error boundaries" priority: 1

Crash Instrumentation

Capture crashes with the context needed to debug them.

Core Principle

A crash report without context is useless. Every crash should include:

Breadcrumb Strategy

Breadcrumbs are the trail leading to a crash. Capture:

Limit: Keep last 20-50 breadcrumbs. More is noise.

Error Boundaries

Catch errors before they crash the app:

// iOS - capture context before crash
func captureError(_ error: Error, screen: String, job: String?) {
    Observability.captureError(error, context: [
        "screen": screen,
        "job_name": job ?? "unknown",
        "session_duration": sessionDuration(),
        "memory_pressure": memoryPressure()
    ])
}

// Android - uncaught exception handler
Thread.setDefaultUncaughtExceptionHandler { thread, throwable ->
    Observability.captureError(throwable, mapOf(
        "thread" to thread.name,
        "screen" to currentScreen,
        "job_name" to currentJob
    ))
    previousHandler?.uncaughtException(thread, throwable)
}

What NOT to Attach

Crash Types to Handle

Implementation

See references/crash-reporting.md for:

• Platform-specific crash capture setup
• Breadcrumb implementation patterns
• Vendor SDK configuration

See skills/symbolication-setup for readable stack traces.