Instead, it could be better to use:

• community pattern: everyone else is doing it. Everyone sees it they know exactly how and why it is there.
• readability pattern: created for the sake of making more readable code. The only true goal is writing code that anyone can reason quickly about.
• performance pattern: squeeze the code for maximum performance, and it can degrade readability.
• guardrail pattern: it exists to avoid known foot guns such as magic number

Often people see "best practices" as community, readability, or guardrail patterns. It is also time as professional that we use a richer vocabulary.