What problem does it solve? Building production-grade structured logging in Go requires wiring together sampling, PII scrubbing, routing, and backend sinks, and mistakes like sampling after formatting or forgetting to flush batch handlers silently waste CPU or lose logs. This Skill provides the canonical pipeline patterns and correct constructor usage for the 20+ samber/slog-* handler packages. ## Core Features & Use Cases - Pipeline composition: Combine slog-multi patterns (Fanout, Router, FirstMatch, Failover, Pool, Pipe) with slog-sampling and slog-formatter in the correct ordering. - HTTP middleware setup: Configure slog-gin, slog-echo, slog-fiber, slog-chi, or slog-http with per-status-code log levels and request filters. - Backend sinks and shutdown: Wire Datadog, Sentry, Loki, Kafka, Slack, and other sinks with the Option{}.NewXxxHandler() pattern and required graceful-shutdown flushes. - Use Case: Route ERROR logs to Sentry unsampled while sampling INFO logs at 10% into Loki, with PII scrubbed before any record leaves the process. ## Quick Start Set up a slog pipeline in Go using samber/slog libraries that samples info logs at 10%, scrubs PII, and routes errors to Sentry with graceful shutdown.