Menú
Track user journeys with intent context and friction signals. Use when instrumenting funnels or multi-step flows.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Instrument API requests with spans and distributed tracing. Use when tracking request latency or debugging API issues.
Monitor JavaScript bundle size and execution performance. Use when tracking bundle size, identifying large chunks, or optimizing load performance.
Measure and optimize Core Web Vitals (LCP, INP, CLS). Use when implementing CWV tracking or debugging performance.
Set up error tracking with actionable context. Use when configuring error capture or error boundaries.
Measure SSR hydration timing and issues. Use when tracking hydration performance, debugging hydration mismatches, or optimizing SSR/SSG applications.
Plan what to measure in web applications. Use when starting observability or prioritizing instrumentation.
| name | user-journey-tracking |
| description | Track user journeys with intent context and friction signals. Use when instrumenting funnels or multi-step flows. |
| triggers | ["track user journey","funnel instrumentation","drop-off analysis"] |
| priority | 2 |
Instrument flows to answer: "Why did users fail to complete their intended task?"
Every event should include intent context:
| Field | Example | Why |
|---|---|---|
job_name | "checkout" | Which user goal |
job_step | "payment" | Where in the journey |
job_progress | "3/4 steps" | How far they got |
Detect when users are struggling:
| Signal | Detection | Indicates |
|---|---|---|
| Rage clicks | 3+ clicks on same element within 1s | UI unresponsive |
| Retry exhaustion | 3+ retries of same action | Persistent failure |
| Quick abandonment | Exit within 5s of error | Lost trust |
| Form thrashing | Repeated focus/blur on same field | Confusion |
| Back loops | 3+ backs without progress | Lost/confused |
| Event | When |
|---|---|
journey.started | User begins multi-step flow |
journey.step_complete | User advances to next step |
journey.friction | Friction signal detected |
journey.success | User completes goal |
journey.abandoned | User exits without completing |
Use Read tool to load references/user-focused-observability.md for detailed patterns.
skills/instrumentation-planning - JTBD frameworkskills/error-tracking - Enriching errors with journey contextreferences/jtbd.md - Jobs-to-be-Done methodology