Agent skill · software engineering · jeremylongshore
sentry-reference-architecture
Design production-grade Sentry architecture for multi-service organizations.
Why this skill is useful
Provides specific architectural patterns and centralized configuration examples for implementing Sentry in multi-service environments, which the AI wouldn't reliably generate on its own.
What it needs
Requires @sentry/node installed locally. Requires sentry account access. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Reference Architecture Overview Enterprise Sentry architecture patterns for multi-service organizations. Covers centralized configuration, project topology, team-based alert routing, distributed tracing, error middleware, source map management, and a production-ready SentryService wrapper. Prerequisites Sentry organization at sentry.io (Business plan+ for team features) @sentry/node v8+ installed (npm install @sentry/node @sentry/profiling-node) Service inventory and team ownership documented Node.js 18+ (ESM and native fetch instrumentation) Instructions Step 1 — Project Structure Strategy Pattern A: One Project Per Service (3+ services, recommended) Benefits: independent quotas, team-scoped alerts, per-service rate limits, isolated release tracking. Pattern B: Shared Project (< 3 services, single team) — one project with Environment tags (production/staging/dev). Simpler setup; outgrow when alert noise exceeds one team. Step 2 — Centralized Config Module Create lib/sentry.ts imported by every service to enforce org-wide defaults: Bootstrap in each service: Step 3 — Error Handling Middleware Express: FastAPI (Python): Step 4 — Distributed Tracing HTTP (automatic): SDK v8 auto-propagates sentry-trace + baggage headers on fetch/http. All services in the same org link automatically. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-reference-architecture--801813