From 013ed0a8e6ec5236d8b4d7e7aee9e42ce56f8d1d Mon Sep 17 00:00:00 2001
From: haelyra <49814733+haelyra@users.noreply.github.com>
Date: Wed, 2 Sep 2026 15:47:12 -0400
Subject: [PATCH] fix(rules): make Boolean naming guidance neutral

---
 rules/common/coding-style.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/rules/common/coding-style.md b/rules/common/coding-style.md
index 67404219a..2f5d1c066 100644
--- a/rules/common/coding-style.md
+++ b/rules/common/coding-style.md
@@ -66,7 +66,8 @@ ALWAYS validate at system boundaries:
 Language-independent:
 
 - Descriptive names: the name says what the thing holds or does, without a comment.
-- Booleans read as a claim: prefix with `is`, `has`, `should` or `can`.
+- Boolean names read clearly as claims under the applicable language or package
+  convention.
 - Where the language draws the distinction, constants and types are visually
   distinct from ordinary values in the form its language or package rule defines.