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).

PriorityP2 — style, consistency, readabilityScopeUniversal — language-agnostic, broadly applicable

Exceptions / tradeoffs (EN)Iznimke / tradeoffi (HR)

fullstack ruleP2universalStack: documentation

documentationconsistencycopy-pastereview

Keep version numbers consistent within a single doc example

When a how-to walks through one example version, use the same version string throughout; don't let a copy-paste leave a mismatched number in a later step.

PR: hegnar-zephr-components · org-mining-hist-2026-06Created: Jun 19, 2026

Bad example

Old codebash

1	`# let's say it's v3.5.2`
2	`git switch -c v4.5.2 # mismatched version`

Explanation (EN)

Objašnjenje (HR)

Good example

New codebash

1	`# let's say it's v3.5.2`
2	`git switch -c v3.5.2`

Explanation (EN)

Objašnjenje (HR)

Login required