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, readabilityScopeProject-specific — unique to one codebase/workflow

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

frontend ruleP2project specificStack: React

apideprecationlegacyconvention

Use the current API variant, not the legacy one

When both a current and a *Legacy variant of a component/API exist, use the current one for new code unless there's a documented reason to stay on legacy.

PR: hegnar-forum-web · org-mining-3rd-2026-06Created: Jun 18, 2026

Bad example

Old codetsx

1	`<ZephrFeatureLegacy slug="paywall" />`

Explanation (EN)

Objašnjenje (HR)

Good example

New codetsx

1	`<ZephrFeature slug="paywall" />`

Explanation (EN)

Objašnjenje (HR)

Login required