Audit mobile codebases (iOS, Android, React Native, Flutter) for observability gaps, generate instrumentation plans with priorities and timelines, instrument crashes, performance metrics, network traces, user journeys, and session replays, set up symbolication, and review code changes for telemetry best practices.
npx claudepluginhub nexus-labs-automation/mobile-observabilityExplores mobile codebases to understand architecture, detect existing telemetry, and identify instrumentation opportunities
Reviews code changes for observability quality — anti-patterns, missing context, naming conventions
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
Share bugs, ideas, or general feedback.
Teaches Claude how to instrument mobile apps correctly — what to measure, what context to attach, and what mistakes to avoid.
Most mobile teams instrument poorly:
This 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?"
claude plugin marketplace add calube/mobile-observability
claude plugin install mobile-observability
/instrument ios
/audit features/checkout
"How should I instrument this payment flow?"
"What context should I attach to crashes?"
"Set up session replay with Bitdrift"
"Review this code for observability anti-patterns"
"What's missing from our crash reporting setup?"
| Command | Description |
|---|---|
/instrument [platform] | Generate prioritized instrumentation plan for iOS, Android, React Native, or Flutter |
/audit [path] | Scan existing code for instrumentation gaps and anti-patterns |
Agent definitions that Claude reads and follows when performing analysis tasks.
Explores mobile codebases to understand architecture and identify instrumentation opportunities.
Focus Areas:
Output:
Reviews code changes for observability issues before they ship.
Focus Areas:
Output:
8 skills that activate automatically based on context:
| Skill | Trigger |
|---|---|
instrumentation-planning | "What should I measure?" |
crash-instrumentation | "How to capture crashes with context" |
session-replay | "Set up session replay" |
interaction-latency | "Track button response time" |
navigation-latency | "Track screen load time" |
network-tracing | "Trace API requests" |
user-journey-tracking | "Track user funnels" |
symbolication-setup | "Configure dSYM upload" |
Use this plugin for:
Don't use for:
mobile-observability/
├── commands/ # /instrument, /audit
├── agents/ # codebase-analyzer, instrumentation-reviewer
├── skills/ # 8 instrumentation skills
├── hooks/ # Anti-pattern warnings for Swift/Kotlin/TypeScript/Dart
└── references/ # 25+ guides covering methodology, platforms, vendors
MIT — see LICENSE
Expert guidance and automation for mobile app observability: crash reporting, performance monitoring, session replay, and instrumentation for iOS, Android, React Native, and Flutter.
Use this agent when you need expert assistance with Flutter mobile development tasks, including code analysis, widget creation, debugging, performance optimization, or architectural decisions. Examples: <example>Context: User is working on a Flutter app and faces issues with navigation. user: 'My Navigator.push isn't updating the UI correctly when moving to a new screen' assistant: 'Let me use the flutter-dev agent to analyze your navigation setup and provide a solution' <commentary>Since this is a Flutter-specific navigation issue, use the flutter-dev agent to provide expert guidance on Navigator problems.</commentary></example> <example>Context: User wants to create a custom widget that aligns with their app's design system. user: 'I need to create a custom button widget that matches our app's design system' assistant: 'I'll use the flutter-dev agent to create a button widget that aligns with your existing codebase structure and design patterns' <commentary>The user needs a Flutter widget that follows existing patterns, so use the flutter-dev agent.</commentary></example>
Use this agent when developing native iOS or Android applications, implementing React Native features, or optimizing mobile performance. This agent specializes in creating smooth, native-feeling mobile experiences. Examples:\n\n<example>\nContext: Building a new mobile app\nuser: "Create a TikTok-style video feed for our app"\nassistant: "I'll build a performant video feed with smooth scrolling. Let me use the mobile-app-builder agent to implement native performance optimizations."\n<commentary>\nVideo feeds require careful mobile optimization for smooth scrolling and memory management.\n</commentary>\n</example>\n\n<example>\nContext: Implementing mobile-specific features\nuser: "Add push notifications and biometric authentication"\nassistant: "I'll implement native push notifications and Face ID/fingerprint auth. Let me use the mobile-app-builder agent to ensure proper platform integration."\n<commentary>\nNative features require platform-specific implementation and proper permissions handling.\n</commentary>\n</example>\n\n<example>\nContext: Cross-platform development\nuser: "We need this feature on both iOS and Android"\nassistant: "I'll implement it using React Native for code reuse. Let me use the mobile-app-builder agent to ensure native performance on both platforms."\n<commentary>\nCross-platform development requires balancing code reuse with platform-specific optimizations.\n</commentary>\n</example>
Use this agent when you need expert assistance with Flutter mobile development tasks, including code analysis, widget creation, debugging, performance optimization, or architectural decisions. Examples: <example>Context: User is working on a Flutter app and faces issues with navigation. user: 'My Navigator.push isn't updating the UI correctly when moving to a new screen' assistant: 'Let me use the flutter-dev agent to analyze your navigation setup and provide a solution' <commentary>Since this is a Flutter-specific navigation issue, use the flutter-dev agent to provide expert guidance on Navigator problems.</commentary></example> <example>Context: User wants to create a custom widget that aligns with their app's design system. user: 'I need to create a custom button widget that matches our app's design system' assistant: 'I'll use the flutter-dev agent to create a button widget that aligns with your existing codebase structure and design patterns' <commentary>The user needs a Flutter widget that follows existing patterns, so use the flutter-dev agent.</commentary></example>
Mobile app debugging for iOS, Android, cross-platform frameworks. Use for crashes, memory leaks, performance issues, network problems, or encountering Xcode instruments, Android Profiler, React Native debugger, native bridge errors.
Mobile app test automation with Appium, Detox, XCUITest - test iOS and Android apps