error-monitoring

# Error Monitoring Generator Generates a production-ready error monitoring infrastructure with protocol-based architecture for easy provider swapping. ## When This Skill Activates - User asks to "add crash reporting" or "error monitoring" - User mentions "Sentry", "Crashlytics", or "crash analytics" - User wants to "track errors in production" - User asks about "debugging production issues" ## Pre-Generation Checks (CRITICAL) ### 1. Project Context Detection Before generating, ALWAYS check: ```bash # Check for existing crash reporting rg -l "Sentry|Crashlytics|CrashReporter" --type swift # Check Package.swift for existing SDKs cat Package.swift | grep -i "sentry\|firebase\|crashlytics" # Check for existing error handling patterns rg "captureError|recordError|logError" --type swift | head -5 ``` ### 2. Conflict Detection If existing crash reporting found: - Ask: Replace, wrap existing, or create parallel system? ## Configuration Questions Ask user via AskUserQuestion: 1. **Initial provider?** - Sentry (recommended for indie devs) - Firebase Crashlytics (if already using Firebase) - None (set up infrastructure only) 2. **Include breadcrumbs?** - Yes (track navigation, user actions) - No (errors only) 3. **Include user context?** - Yes (anonymized user ID, app state) - No (minimal data collection) ## Generation Process ### Step 1: Create Core Files **Always generate:** ``` Sources/ErrorMonitoring/ ├── ErrorMonitoringService.swift # Pro...