dry-principle
Use DRY while generating, refactoring, or reviewing code in mixed-language or config-heavy repos. Keep one authoritative representation for change-prone knowledge such as rules, versions, paths, schemas, option lists, and behavior descriptions. Review for duplicated logic and for drift across docs, tests, CI, and config, but avoid premature abstraction when duplication is harmless and clarity matters more.