one-pattern-one-way

Code consistency is enforced by adopting a single, established pattern for each problem category, requiring all existing usages to be refactored when a new pattern is adopted. This eliminates conflicting local shortcuts and ambiguity across the codebase.

Standardizing error handling and data validation requires strict adherence to one documented pattern for each concern. This prevents multiple conflicting conventions and ensures every developer handles these tasks using the same established approach.

Stopping developers from using multiple libraries requires pattern enforcement that dictates a single approach for HTTP clients and logging. This ensures only one established solution is used, removing ambiguity and conflicting local shortcuts.

Refactoring existing code for a new configuration loading pattern is needed whenever a new pattern is adopted. The skill requires adherence to documented patterns and mandates refactoring all existing usages to maintain a single approach.

Pattern enforcement can be applied to managing string constants and default values. It ensures a single established approach is used for these common software engineering concerns, preventing inconsistency and conflicting local shortcuts.