Rules Hub
Coding Rules Library
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
fullstack ruleP2universalStack: configuration
configurationnamingclarity
Name config keys after their specific scope, not a generic label
Give configuration keys descriptive, scope-qualified names so multiple consumers don't collide on an ambiguous generic key.
PR: abcn-web · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codejson
| 1 | { |
| 2 | "metaTags": { /* only used by one section */ } |
| 3 | } |
Explanation (EN)
Objašnjenje (HR)
Good example
New codejson
| 1 | { |
| 2 | "sectionMetaTags": { /* clear which feature owns this */ } |
| 3 | } |
Explanation (EN)
Objašnjenje (HR)