mobile-observability
CLAUDE.md116 starsChanged 11 months agoMITView on GitHub
Claude Code plugin for mobile app observability. Provides commands, agents, skills, and hooks for iOS, Android, and React Native instrumentation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nexus-labs-automation/mobile-observabilityword for word, first seen Dec 20, 2025
Other versions1 project uses a version of this.
Word for word · 1
- nexus-labs-automation/mobile-observability★ 116100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- crash-instrumentationSkill
- instrumentation-planningSkill
- interaction-latencySkill
- navigation-latencySkill
- network-tracingSkill
- session-replaySkill
- symbolication-setupSkill
- user-journey-trackingSkill
The file
Files
Mobile Observability Plugin
Project Context
Claude Code plugin for mobile app observability. Provides commands, agents, skills, and hooks for iOS, Android, and React Native instrumentation.
Plugin Components
| Component | Location | Description |
| Commands | commands/ | /instrument, /audit |
| Agents | agents/ | codebase-analyzer, instrumentation-reviewer |
| Skills | skills/ | 8 focused instrumentation skills |
| Hooks | hooks/hooks.json | Anti-pattern warnings for Swift/Kotlin/TypeScript |
| References | references/ | 20+ guides, templates, vendor docs |
Key Commands
/instrument ios # Generate instrumentation plan
/audit # Scan existing instrumentationSkills
| 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" |
Reference Navigation
| Topic | File |
| Methodology | references/user-focused-observability.md |
| What to measure | references/jtbd.md |
| Instrumentation checklist | references/instrumentation-patterns.md |
| Business logic | references/business-logic.md |
| Feature flags | references/feature-flags.md |
| Crashes | references/crash-reporting.md |
| Performance | references/performance.md, references/ui-performance.md |
| Database | references/data-persistence.md |
| iOS | references/ios-native.md |
| Android | references/android-native.md |
| React Native | references/react-native-expo.md |
| OpenTelemetry | references/otel-mobile.md |
| Vendors | references/platforms/*.md |
Development
# Test plugin locally
claude plugins install ./
# Verify structure
ls -la .claude-plugin/ commands/ agents/ skills/ hooks/ references/Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.