Does this skill support structured logging for all log levels?

Structured LogRecord patterns are mandatory for INFO, WARN, ERROR, and FATAL levels, while direct logging is permitted for DEBUG and TRACE levels.

Why does this skill forbid direct use of SLF4J or Log4j?

The CUI standards require the CuiLogger wrapper to ensure consistent metadata, structured formatting via LogRecord, and better integration with the CUI ecosystem.

Can this skill help with documentation?

Yes, it includes specific standards for generating AsciiDoc documentation for LogMessages classes to keep system documentation in sync with the code.

What is the rule for exception parameters in this skill?

To maintain consistency, the exception parameter must always come first in all logging calls (e.g., LOGGER.error(exception, message)).

CUI Logging Standards

Name: CUI Logging Standards
Author: cuioss

bycuioss

Analytics & Monitoring

Enforces standardized Java logging patterns using CuiLogger and LogRecord for structured, reliable application observability.

About

The CUI Logging skill equips Claude with specialized knowledge to implement and maintain Java logging according to CUI standards. It ensures the exclusive use of CuiLogger while prohibiting direct SLF4J or Log4j calls, mandates structured LogRecord patterns for high-severity levels, and enforces specific exception handling rules. This skill is critical for developers working within the cui-java-tools ecosystem who need to maintain consistency, reliability, and predictable log outputs across their orchestration layers and services.

Key Features

Standardized exception-first parameter ordering for all error logs
0 GitHub stars
Strict enforcement of CuiLogger usage over SLF4J and Log4j
Automated AsciiDoc documentation patterns for logging components
Structured LogRecord implementation for INFO, WARN, and ERROR levels
DSL-style LogMessages class generation with @UtilityClass patterns

Use Cases

Migrating legacy SLF4J or Log4j logging calls to the CUI logging framework
Standardizing error handling and exception logging across large-scale Java repositories
Building type-safe, DSL-based log message constants for Java microservices

About

Key Features

Standardized exception-first parameter ordering for all error logs
0 GitHub stars
Strict enforcement of CuiLogger usage over SLF4J and Log4j
Automated AsciiDoc documentation patterns for logging components
Structured LogRecord implementation for INFO, WARN, and ERROR levels
DSL-style LogMessages class generation with @UtilityClass patterns

Use Cases

Migrating legacy SLF4J or Log4j logging calls to the CUI logging framework
Standardizing error handling and exception logging across large-scale Java repositories
Building type-safe, DSL-based log message constants for Java microservices