Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
/plugin marketplace add calube/mobile-observability/plugin install mobile-observability@caleb-davis-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Strategic guidance for what to measure using Jobs-to-be-Done framework.
For each user job, ask:
| Tier | Focus | Examples |
|---|---|---|
| 1 | Crashes & errors | Crash reporting, error boundaries |
| 2 | User context | User ID, session ID, device info |
| 3 | Performance | App start, screen load, network |
| 4 | Breadcrumbs | Navigation, user actions |
| 5 | Business metrics | Funnels, feature usage |
Day 1: Crash reporting + User context
Week 1: Breadcrumbs + Release tracking
Week 2: Performance spans
Month 1: Business metrics
Use OTel-compatible span/attribute names now (zero cost, easier migration later):
http.request.method not methodui.screen.load not screenLoadapp.start.cold not coldStartSee references/otel-mobile.md for full naming conventions.
See references/instrumentation-patterns.md for:
See references/jtbd.md for full Jobs-to-be-Done framework.
skills/user-journey-tracking for implementing JTBD instrumentationskills/crash-instrumentation for Tier 1 (crashes)skills/symbolication-setup for Tier 1 (readable stack traces)Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.