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 ruleP2project specificStack: css
cssresponsivebreakpoints
Choose responsive breakpoint ranges based on the actual configured breakpoints
When using `down`/`only` breakpoint helpers, include the last supported breakpoint your config defines for that range so the rule actually covers the intended viewport widths. Breakpoint naming is easy to misread.
PR: frontpage-web · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codescss
| 1 | @include breakpoint(small only) { ... } // misses the 451-767px range you intended |
Explanation (EN)
A misread helper name can leave an intended viewport interval uncovered.
Objašnjenje (HR)
Good example
New codescss
| 1 | @include breakpoint(medium-large down) { ... } // covers everything below the large breakpoint |
Explanation (EN)
Objašnjenje (HR)
Notes (EN)
Resolve breakpoint names against the actual configured values and compile the helper to verify the generated interval.
Exceptions / Tradeoffs (EN)
Names such as small, medium-large and down are project/framework conventions, not universal widths. Do not copy a range from another repository.