From 5fa2fef1b1a2d0d986a5996d4cfe3dc4124d51e8 Mon Sep 17 00:00:00 2001 From: Kevin Wang Date: Sun, 19 Jul 2026 20:27:11 -0700 Subject: [PATCH] docs: clarify log message capitalization guidance --- CLAUDE.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index fb39cc38c..beb9d19df 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -146,11 +146,12 @@ forge clean ### Logging and Error Messages -- **Never capitalize** the first letter of log messages and error messages +- Start log messages and error messages with lowercase text +- Preserve the conventional capitalization of identifiers and acronyms when they + begin a message (for example, `RIM`, `OCSP`, or `HTTP`) - Example: `log::info!("starting server on port {}", port);` - Example: `anyhow::bail!("failed to connect to server");` - -This rule is enforced in `.cursorrules`. +- Example: `log::warn!("RIM upstream is unavailable");` ## Key Security Concepts