Set up error tracking with actionable context. Use when configuring error capture or error boundaries.
Capture errors with actionable context like route, user segment, and job step. Use when setting up error boundaries, SDKs, or handling unhandled exceptions and promise rejections.
/plugin marketplace add nexus-labs-automation/web-observability/plugin install nexus-labs-automation-web-observability@nexus-labs-automation/web-observabilityThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Capture errors with the context needed to debug them.
An error without context is useless. Every error should include:
| Context | Why | Example |
|---|---|---|
route | Where it happened | "/checkout" |
job_name | What user was doing | "checkout" |
job_step | Where in the flow | "payment" |
user_segment | Who's affected | "premium" |
app_version | Release correlation | "1.2.3" |
| Type | Capture Method |
|---|---|
| Unhandled exceptions | window.onerror, SDK auto-capture |
| Promise rejections | window.onunhandledrejection |
| Component errors | Error boundaries |
| Async/await errors | try/catch with context |
| API errors | Fetch/axios interceptors |
| Don't | Why |
|---|---|
| Passwords | Security |
| Email/phone | PII |
| Full request bodies | PII, size limits |
| Entire app state | Unbounded |
| Localized messages | Breaks grouping |
See templates/error-boundary.tsx for React error boundary with telemetry.
Use Read tool to load template when generating implementation.
See references/anti-patterns.md for common error tracking mistakes.
skills/source-map-setup - Readable stack tracesskills/api-tracing - API error correlationreferences/frameworks/*.md - Framework-specific error handlingUse 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.