UseUtilityClass's documentation doesn't define "utility class", which makes it uncertain what we're talking about. ClassNamingConventions doesn't either, and in effect the two implementations are separate, and inconsistent.

If we agree on a single definition, we could make sure that ClassNamingConventions and UseUtilityClass (and possibly other rules) stay synchronized in their definition, and reuse implementations.