What problem does it solve? Scattered console.log statements and unstructured log lines make production debugging painful because you cannot query logs by user, request, or business context. This Skill guides you to emit one context-rich wide event per request per service, turning logs into queryable data. ## Core Features & Use Cases - Wide Event Pattern: Consolidate all request context into a single structured JSON event emitted in a finally block, covering timing, status, errors, and business data. - Context & Cardinality Rules: Enforce high-cardinality fields (user IDs, request IDs), business context (subscription tier, cart value), and environment metadata (commit hash, region, version) in every event. - Structure & Anti-Pattern Guidance: Standardize on a single logger, middleware-based event collection, JSON format, consistent schemas, and two log levels while avoiding scattered logs and missing request correlation. - Use Case: When a premium customer reports a failed checkout, query your logs by request_id and instantly see the full event: user subscription, cart total, feature flags, error type, and the exact commit hash deployed. ## Quick Start Ask the AI to review your request handler's logging and refactor it to emit a single wide event with user, business, and environment context.
