Rules Hub
Code Ruleset
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
frontend ruleP2universalStack: react
lintingtoolinghooksconventions
Set up lint guardrails before adopting a new language/library feature
When introducing a new API with usage rules (e.g. hooks), add the matching lint rules first so the team's usage is enforced from the start.
PR: frontpage-web · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codejavascript
| 1 | // start using a new feature project-wide with no lint rule guarding correct usage |
Explanation (EN)
Unenforced API constraints are easy to violate during widespread adoption.
Objašnjenje (HR)
Good example
New codejavascript
| 1 | // enable the recommended lint rules for the feature, then adopt it |
Explanation (EN)
Objašnjenje (HR)
Notes (EN)
Before broad adoption of an API with checkable usage constraints, inspect existing lint support and enable compatible rules within the authorized repository configuration scope.
Exceptions / Tradeoffs (EN)
No suitable rule means use targeted tests and review. Installing personal checks into a company repo still requires an explicit request.