Domain-Focused Naming

Domain-focused naming improves readability by describing what code does rather than exposing implementation details. Remove technical specifics like library names, protocols, and pattern references—rename "ZodValidator" to "Validator"—so names reflect business intent and remain stable across refactors.

Implementation-detail names create maintenance debt when underlying technology changes. Names tied to how code works rather than what it does force renames during refactors and obscure intent. Domain-focused names survive implementation swaps and communicate purpose directly to readers.

Temporal references like "New", "Improved", and "Legacy" become meaningless over time and clutter codebases with historical context. Replace them with stable, domain-aligned names that describe function or responsibility instead, ensuring names remain relevant across project lifecycles.

Refactor names during review when they expose implementation choices, reference patterns, or contain temporal markers that don't reflect domain meaning. Domain-focused naming prevents confusion, improves maintainability, and makes intent clear to future readers without requiring context about how something was built.

Avoid names that leak implementation—library names, protocol references, technical abbreviations—and temporal markers that lose meaning over time. Enforce domain-aligned naming across variables, functions, classes, modules, and APIs so all identifiers describe what code does, not how it achieves it.