evlog

Use this skill when work touches evlog — wide events, structured errors, drains, sampling, audit trails, AI SDK / eve telemetry, CLI product telemetry, client logging, plugins, or @evlog/cli map coverage scoring.

Snapshot: evlog@2.29.0, @evlog/cli@0.6.3, @evlog/telemetry@0.3.1 (verified 2026-10-01; no newer releases). Refresh from source-map.md if versions differ.

Workflow

1. Inspect the local logging surface before changing code:
   • Package versions for evlog, optional @evlog/cli / @evlog/telemetry / @evlog/nuxthub, framework peers, and drain destinations in use.
   • Integration path: Nuxt/Nitro module, Next createEvlog/withEvlog, TanStack Start evlog/nitro/v3, Hono/Express/Fastify/Elysia middleware, Workers, Astro/Lambda guides, standalone initLogger.
   • Patterns: scattered console/pino lines vs log.set wide events, createError({ why, fix }), audits, AI wraps, eve hooks, client ingest, plugins.
2. Refresh docs when versions or APIs are unclear. Start from source-map.md.
3. For install, three logging modes, initLogger, and core APIs, use setup-core.md.
4. For wide-event design, sealing/fork, structured errors, catalogs, and redaction, use wide-events-errors.md.
5. For framework wiring and adapter choice, use frameworks-adapters.md.
6. For pipelines, sampling, audit, AI, client logs, and evlog map/CI, use cli-advanced.md.
7. For plugins, stream, diagnostics, toolkit, @evlog/telemetry, and evlog/eve, use extend.md.