القائمة
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
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.
| name | instrumentation-planning |
| description | Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?" |
| triggers | ["planning telemetry","prioritize instrumentation","start observability","what should I track","what to measure","where to begin"] |
| priority | 1 |
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)