cui-logging

Enforce CUI logging standards with LogRecord templates in Java modules.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill cui-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cui-logging
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-dev-java-cui/skills/cui-logging
Command: npx skills add https://github.com/cuioss/plan-marshall --skill cui-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes uniform, compliant logging across Java projects by enforcing the CUI logging standards and structured LogRecord usage.

Core Features & Use Cases

  • CuiLogger usage, LogRecord templates, and the DSL-style LogMessages pattern.
  • Migration and maintenance guidance, documentation references, and testing patterns.
  • On-demand loading of standards to reference material during tasks.

Quick Start

Load the core logging standards and begin applying the LogRecord-based guidelines in new code.

Frequently Asked Questions about cui-logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Java logging using CuiLogger and LogRecord templates?

Standardize Java logging by enforcing CUI logging standards with LogRecord templates, applying consistent INFO, WARN, ERROR, and FATAL messages alongside DSL-style LogMessages definitions across modules using the CuiLogger framework.

What is the DSL-style LogMessages pattern for Java production logging?

The DSL-style LogMessages pattern is a structured approach enforcing exception-first arguments and %s substitutions within LogRecord templates, ensuring uniform and compliant logging across Java projects using the CuiLogger framework.

How do I migrate existing Java log messages to CUI logging standards?

Migrate existing log messages to CUI logging standards by applying LogRecord templates with consistent INFO/WARN/ERROR/FATAL definitions, using the DSL-style LogMessages pattern with exception-first arguments and %s substitutions.

Does CuiLogger support exception-first argument ordering in LogRecord templates?

CuiLogger supports exception-first argument ordering within LogRecord templates, enforcing this pattern through the DSL-style LogMessages definitions to maintain consistent and compliant logging across Java modules.

What are the limitations of enforcing CUI logging standards across Java modules?

Limitations include the requirement to use the CuiLogger framework exclusively and maintain corresponding LogMessages definitions for all log levels, which can increase boilerplate when applying CUI logging standards across diverse Java modules.