What problem does it solve? Adding structured os.log logging to Swift types normally requires hand-written OSLog storage, availability-gated branches for pre-macOS 11 systems, and repetitive subsystem/category boilerplate. This Skill teaches how to use the @Loggable and #log macros from FrameworkToolbox to generate all of that logging infrastructure with zero protocol conformance and zero boilerplate. ## Core Features & Use Cases - Macro-based logger synthesis: Apply @Loggable to a struct, class, enum, or actor to synthesize subsystem, category, _osLog, and logger members, with configurable access level, subsystem, and category. - Unified #log expression macro: Emit log lines that call os.Logger on macOS 11+/iOS 14+ and automatically fall back to the legacy os_log C API on older OS versions, with correct level mapping (.default to notice, .fault to critical). - Privacy, formatting, and named categories: Control privacy levels (.public/.private/.sensitive/.auto), numeric formats, string alignment, and route logs through shared named categories declared as static LogCategory members. - Use Case: While building a networking layer in a Swift framework, annotate APIClient with @Loggable(.internal, subsystem: "com.acme.networking", category: "API") and use #log(.info, ...) calls with privacy-annotated interpolations to get Console.app-filterable diagnostics that also work on iOS 13. ## Quick Start Ask the AI to add @Loggable to your Swift type and insert #log calls with appropriate levels and privacy annotations for its key operations.
