Structured Logging Skill

Two tiers. Tier 1 is non-negotiable. Tier 2 requires judgment. Rule 0 overrides both.

Rule 0 — Follow the project first, always

Before adding any log, check the codebase: existing logger (Winston/Pino, structlog/loguru, Serilog/zap…)? Existing field naming (user_id vs userId)? Existing redaction/PII-scrubbing utility? Existing audit-log pipeline (e.g. a dedicated audit_logs table/service instead of stdout)? If the project already has a pattern for something below, use it — it wins over every default in this skill. Only apply the defaults below on a new project, or where the project has no established pattern yet. Never rename an established field (status_code → statusCode); reuse it.