Logging Setup
# 08 — Structured JSON logging
## Context
Use this when a service's output is `print()` calls and one-off
`logger.info("user %s did thing", x)` lines — the kind of logging
that's fine in dev and unparseable in prod. Goal: every log line is
JSON, one line per event, with a stable schema your log aggregator
can index.
## Templatewhen to use it
Community prompt sourced from the open-source GitHub repo thunderstornX/cursor-vibe-starter (MIT). A "Logging Setup" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
thunderstornX/cursor-vibe-starter · MIT