evlog

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

Workflow

1. Inspect the local logging surface before changing code:
   • Package versions for evlog, optional @evlog/cli, 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, standalone initLogger, Workers, etc.
   • Patterns: scattered console/pino lines vs log.set wide events, createError({ why, fix }), audits, AI wraps, client ingest.
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.

Implementation Judgment