Loading...
Loading...
Found 13 Skills
Implement structured logging with JSON formats, log levels (DEBUG, INFO, WARN, ERROR), contextual logging, PII handling, and centralized logging. Use for logging, observability, log levels, structured logs, or debugging.
Expert logging guidance based on Boris Tane's loggingsucks.com philosophy. Use when implementing logging, adding observability, debugging production issues, or reviewing code that includes log statements. Covers wide events architecture, structured logging, smart sampling, and high-cardinality field design.
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
Logging best practices for applications and services including structured logging, log levels, and log management strategies
Structured logging with proper levels, context, PII handling, centralized aggregation. Use for application logging, log management integration, distributed tracing, or encountering log bloat, PII exposure, missing context errors.
Python logging with loguru and platformdirs. TRIGGERS - loguru, structured logging, JSONL logs, log rotation, XDG directories.
Best practices and guidelines for using logger in API routes. Defines appropriate logging levels, what to log, and when to avoid logging. Use when implementing or reviewing API route logging, debugging strategies, or optimizing log output.
C# error handling, validation, and Result pattern best practices. Use when handling exceptions, implementing validation, designing error responses, or choosing between exceptions and Result types.
Implement secure error handling to prevent information leakage and provide appropriate error responses. Use this skill when you need to handle errors in API routes, prevent stack trace exposure, implement environment-aware error messages, or use the error handler utilities. Triggers include "error handling", "handle errors", "error messages", "information leakage", "stack trace", "handleApiError", "production errors", "error responses".
Adds structured JSON logging, correlation/trace IDs, metrics, and health endpoints. Use when wiring observability for a new service, debugging cross-service requests, or removing console.log.
Inject high-value structured logging while writing or refactoring code. Use whenever generating, editing, or reviewing backend/service code (APIs, handlers, jobs, scripts) so errors are always caught and logged, and other important logging is added based on real risk of failure — not sprinkled everywhere. Trigger on requests like "add logging", "write this endpoint/handler/function", "refactor this service", or any code that talks to a DB, external API, queue, or has business logic with branching.
Use before writing or editing any Python code — scripts, functions, bug fixes, cron jobs, data-processing one-offs, or additions to an existing .py file — even if the request sounds quick, casual, or "just a simple script." Applies whether the user names a .py file, describes what the script should do, or asks you to add/fix a function in Python. Covers required standards: type hints, no global variables, logging instead of print, wrapping any I/O (HTTP, DB, subprocess, file) in try/except, commenting the why not the what, writing a real test, and where to place design docs. Does not apply to conceptual Python questions with no code to write (e.g. explaining language features, comparing list vs tuple, explaining what an existing traceback means when the user hasn't asked for a fix, package install help, or learning-resource recommendations), and does not apply to non-Python languages.