What problem does it solve? Developers working on the yeaboi codebase risk creating inconsistent log files, hardcoding paths, or flooding per-frame render code with log calls. This Skill centralizes all logging rules so every handler, log directory, and log level follows one convention defined in logging_setup.py and paths.py. ## Core Features & Use Cases - Central handler setup: All FileHandler creation goes through src/yeaboi/logging_setup.py with one shared format, rotation (2 MB, 3 backups), and a WARNING fallback level. - Mode and session log routing: Use the mode_log context manager for per-mode logs (standup, retro, performance, reporting, analysis) and attach_session_log for per-planning-session logs under ~/.yeaboi/logs/. - Runtime level control: Change verbosity live via the LOG_LEVEL env var or the Settings page, which calls apply_level() to retune all attached handlers. - Use Case: When adding a new mode page to the TUI, wrap its runner in with mode_log("mymode"): so all records route to ~/.yeaboi/logs/mymode/mymode.log without writing any handler boilerplate. ## Quick Start Ask the AI to add logging to a new mode page following the central logging rules in logging_setup.py.