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: language-agnostic

namingconsistencyproject-structureclean-code

Use one consistent file-naming case across a module

Don't mix camelCase and kebab-case filenames for sibling utilities; pick one convention. Also merge tiny related utility files into a cohesive module.

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

Bad example

Old codetext

1	`src/utils/findByCategoryId.ts`
2	`src/utils/search-bar.ts // mixed casing, both category helpers`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetext

1	`src/utils/categoryUtils.ts // one consistent name, related helpers together`

Explanation (EN)

Objašnjenje (HR)

Login required