Plan backend observability using RED + USE + 4 Golden Signals + JTBD
Plans backend observability using RED, USE, 4 Golden Signals, and JTBD frameworks. Triggers when you need to instrument services, databases, or resources with prioritized metrics tied to user jobs.
/plugin marketplace add nexus-labs-automation/backend-observability/plugin install nexus-labs-automation-backend-observability@nexus-labs-automation/backend-observabilityThis skill inherits all available tools. When active, it can use any tool Claude has access to.
"What job is this telemetry helping someone accomplish?"
Every metric/span should answer a job. If you can't name the job, don't add the telemetry.
| Service Type | Use |
|---|---|
| HTTP/gRPC APIs | RED (Rate, Errors, Duration) |
| Resources (pools, memory) | USE (Utilization, Saturation, Errors) |
| Comprehensive SRE | 4 Golden Signals |
| Tier | What | Examples |
|---|---|---|
| T0: Foundation | Must have | Service tags, HTTP middleware, error tracking, health checks |
| T1: Performance | Should have | RED per endpoint, DB tracing, external service spans, context propagation |
| T2: Resources | Should have | USE for pools, memory/GC, queue depth |
| T3: Business | Nice to have | JTBD tags, user tier, feature flags |
| T4: Resilience | Nice to have | Circuit breaker state, retry counts, timeouts |
Link observability to user value:
| Job | Success | Failure | Friction |
|---|---|---|---|
| "Place order" | Order created <2s | Order error | Retries >0, duration >5s |
| "Process payment" | Payment success | Declined | Gateway timeout |
Present prioritized instrumentation plan organized by tier, with specific metrics and implementation order.
Load based on need:
references/methodology/red-methodology.mdreferences/methodology/use-methodology.mdreferences/methodology/four-golden-signals.mdreferences/methodology/jtbd-for-backend.mdUse 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.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
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.