naming-consistency

a second convention introduced into a domain that already standardized on one

Agent checkadvisory by defaultbasecode

The argument

Naming Consistency

Standardize patterns within each domain — if the codebase already uses one, follow it; never introduce a competing convention:

Data fetching: one of getData / fetchData / loadData, not a mix
Booleans: consistent prefixes (is, has, should, can)
Event handlers: one pattern (onSubmit vs handleSubmit)

Subordinate to Naming Consistency above: a domain that already standardized on fetchData keeps its verb — the vocabulary governs new domains.

The proof

failsrc/orders/orderIsPaid.ts

// A second boolean convention in a domain whose other predicates read `isX`.
export const orderIsPaid = ({ paidAt }: { paidAt: string | null }): boolean => paidAt !== null;

passsrc/orders/isOrderPaid.ts

// The domain already prefixes its booleans with `is`, so this one does too.
export const isOrderPaid = ({ paidAt }: { paidAt: string | null }): boolean => paidAt !== null;

Turn it down

Both lines go in your lightsout.config.json.

"standards-checks": { "naming-consistency": "advisory" }

"standards-checks": { "naming-consistency": "off" }