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: any
organizationnamingciconventions
Namespace shared config/asset paths to avoid future clashes
When a path could collide with a framework convention later (e.g. .github/actions), use a namespaced folder name so adding the convention later won't conflict.
PR: hegnar-bellsheep-web · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codeyaml
| 1 | # checks out into .github/actions — clashes if we later add real composite actions |
Explanation (EN)
Objašnjenje (HR)
Good example
New codeyaml
| 1 | # .github/hegnar-actions — namespaced to avoid clash |
Explanation (EN)
Objašnjenje (HR)