generators-error-monitoring

Implement protocol-based error monitoring with swappable provider adapters for iOS/macOS apps.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill generators-error-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generators-error-monitoring
Source: https://github.com/AutisticAF/claude-code-apple-dev-plugin/tree/main/skills/generators-error-monitoring
Command: npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill generators-error-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Error monitoring is challenging to implement and maintain across multiple providers. This skill provides a protocol-based error monitoring layer with a central singleton and swappable provider adapters to simplify production monitoring while preserving testability and privacy.

Core Features & Use Cases

  • Protocol-based interface: a single ErrorMonitoringService protocol that supports configure, captureError, captureMessage, addBreadcrumb, setUser, and reset.
  • Provider adapters: switch between Sentry, Crashlytics, or a NoOp testing mode without code changes.
  • Central integration patterns: app lifecycle, environment access, and mock/testing utilities for CI.

Quick Start

Configure ErrorMonitoring at app launch and select a provider to enable production crash reporting.

Frequently Asked Questions about generators-error-monitoring

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

FAQPage Schema
How do I add crash reporting to an iOS app with swappable providers?

Add crash reporting to iOS using a protocol-based ErrorMonitoringService interface with a central singleton and provider adapters. This enables swappable crash reporting providers without code changes across development stages.

Can I switch between Sentry and Crashlytics without changing app code?

You can switch between Sentry, Crashlytics, or a NoOp testing mode without code changes using provider adapters. The protocol-based interface centralizes error monitoring configuration behind a single ErrorMonitoring singleton.

What is a protocol-based error monitoring architecture for macOS apps?

A protocol-based error monitoring architecture for macOS defines a reusable ErrorMonitoringService protocol supporting configure, captureError, captureMessage, addBreadcrumb, setUser, and reset operations. It simplifies production monitoring while preserving testability and privacy safeguards.

How do I set up breadcrumbs and user context for production error monitoring?

Set up breadcrumbs and user context for production error monitoring through the ErrorMonitoringService protocol. It supports addBreadcrumb, setUser, and reset functions alongside provider integration patterns and privacy safeguards for iOS and macOS applications.

Does this error monitoring approach support mock and testing utilities for CI?

This error monitoring approach supports mock and testing utilities for CI through a NoOp provider mode. The protocol-based architecture with provider adapters enables testability without affecting production crash reporting workflows.