{
  "markdown": "# Mobile Observability Plugin\n\nTeaches Claude how to instrument mobile apps correctly — what to measure, what context to attach, and what mistakes to avoid.\n\n## The Problem\n\nMost mobile teams instrument poorly:\n\n- **Too little** — Can't debug production issues\n- **Too much** — Noise, cost, battery drain\n- **Wrong context** — Errors without enough data to act on\n\nThis plugin teaches Claude to capture both **user intent** (what they tried to do) and **system state** (device conditions, errors, performance) so you can answer *\"Why did this fail, and for whom?\"*\n\n## Installation\n\n```bash\nclaude plugin marketplace add calube/mobile-observability\nclaude plugin install mobile-observability\n```\n\n## Usage\n\n### Commands\n\n```\n/instrument ios\n/audit features/checkout\n```\n\n### Natural Prompts\n\n```\n\"How should I instrument this payment flow?\"\n\"What context should I attach to crashes?\"\n\"Set up session replay with Bitdrift\"\n\"Review this code for observability anti-patterns\"\n\"What's missing from our crash reporting setup?\"\n```\n\n## Commands\n\n| Command | Description |\n|---------|-------------|\n| `/instrument [platform]` | Generate prioritized instrumentation plan for iOS, Android, React Native, or Flutter |\n| `/audit [path]` | Scan existing code for instrumentation gaps and anti-patterns |\n\n## Agents\n\nAgent definitions that Claude reads and follows when performing analysis tasks.\n\n### codebase-analyzer\n\nExplores mobile codebases to understand architecture and identify instrumentation opportunities.\n\n**Focus Areas:**\n- Platform and architecture detection (MVVM, TCA, Clean Architecture)\n- Existing telemetry SDK inventory\n- Entry points and key user flows\n- Network, persistence, and state management layers\n\n**Output:**\n- Platform summary with language/version\n- Architecture pattern identification\n- Existing SDK coverage assessment\n- Gap analysis with priority ranking\n\n### instrumentation-reviewer\n\nReviews code changes for observability issues before they ship.\n\n**Focus Areas:**\n- Anti-patterns (PII leaks, high cardinality, sync telemetry)\n- Missing context (no user ID, no session, no screen)\n- Naming consistency\n- Vendor best practices\n\n**Output:**\n- Issues by severity with file:line references\n- Specific fixes with code examples\n- Vendor guideline references\n\n## Skills\n\n8 skills that activate automatically based on context:\n\n| Skill | Trigger |\n|-------|---------|\n| `instrumentation-planning` | \"What should I measure?\" |\n| `crash-instrumentation` | \"How to capture crashes with context\" |\n| `session-replay` | \"Set up session replay\" |\n| `interaction-latency` | \"Track button response time\" |\n| `navigation-latency` | \"Track screen load time\" |\n| `network-tracing` | \"Trace API requests\" |\n| `user-journey-tracking` | \"Track user funnels\" |\n| `symbolication-setup` | \"Configure dSYM upload\" |\n\n## When to Use\n\n**Use this plugin for:**\n- Adding observability to a new or existing mobile app\n- Setting up crash reporting, performance monitoring, or session replay\n- Choosing between vendors (Sentry, Datadog, Embrace, Bitdrift, Firebase, New Relic, etc.)\n- Reviewing instrumentation code for anti-patterns\n- Understanding what context to attach to errors\n\n**Don't use for:**\n- Backend/server observability\n- Web frontend (different patterns)\n- General logging questions unrelated to mobile\n\n## Directory Structure\n\n```\nmobile-observability/\n├── commands/       # /instrument, /audit\n├── agents/         # codebase-analyzer, instrumentation-reviewer\n├── skills/         # 8 instrumentation skills\n├── hooks/          # Anti-pattern warnings for Swift/Kotlin/TypeScript/Dart\n└── references/     # 25+ guides covering methodology, platforms, vendors\n```\n\n## Philosophy\n\n1. **Start with crashes** — Get crash reporting and symbolication right before adding anything else\n2. **Context over volume** — One error with full context beats 100 without\n3. **User intent + system state** — Link what users tried to do with device conditions (memory, network, battery)\n4. **Avoid anti-patterns early** — PII leaks and high cardinality are expensive to fix later\n\n## Author\n\n[Caleb Davis](https://github.com/calube)\n\n## License\n\nMIT — see [LICENSE](LICENSE)\n",
  "bytes": 4165,
  "sha": "3858ff347d576aa311a501df1c08b1443c53cf6d1abfe9023bccfad0251d4066",
  "repo_slug": "nexus-labs-automation/mobile-observability",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/skl_nexus_labs_automation_mobile_observabili_1142f158/readme"
}