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: universal

processcollaborationdecision-makingreview

Raise high-impact technical decisions with the team before implementing

For changes with broad impact (new dependencies, cross-cutting patterns), seek the team's input in a shared channel before building, rather than implementing and having a single reviewer weigh in afterward.

PR: frontpage-web · org-mining-hist-2026-06Created: Jun 18, 2026

Bad example

Old codetext

1	`// silently add a new third-party lib + new browser API, then open PR`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetext

1	`// post the proposal in the team channel, gather input, then implement`

Explanation (EN)

Objašnjenje (HR)

Login required