Rules Hub
Coding Rules Library
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
Write like a human, avoid AI-tell punctuation and phrasing
Never use the em-dash (—) or other AI-signature symbols and phrasings in any written output: code comments, commit messages, PR and issue descriptions, docs, READMEs. Use plain human punctuation instead (hyphens, commas, colons, parentheses, or separate sentences) and avoid formulaic AI flourishes so the text reads as if a person wrote it.
Bad example
| 1 | Reworked the layout — moved Winners/Losers into a shared section — and it's not just cleaner, it's faster. |
Explanation (EN)
The em-dash (—) plus tidy parallel clauses and the 'it's not just X, it's Y' construction are classic AI writing tells.
Objašnjenje (HR)
Good example
| 1 | Reworked the layout: moved Winners/Losers into a shared section, which is cleaner and a bit faster. |
Explanation (EN)
Plain punctuation (colon, comma) and a natural, slightly uneven sentence read as human-written.
Objašnjenje (HR)
Notes (EN)
Applies to every piece of prose: chat, PR/issue descriptions, commit messages, code comments, docs, READMEs. Tells to avoid beyond the em-dash: rule-of-three lists, heavy parallel/symmetrical structure, 'it's not just X, it's Y', excessive hedging, and over-polished bullet symmetry. Prefer hyphens, commas, colons, parentheses, or just shorter separate sentences.
Exceptions / Tradeoffs (EN)
A literal hyphen in ranges or compound words is fine. This targets the em-dash (—) and AI-flavored phrasing, not normal hyphenation.