Rules Hub
Code Ruleset
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 em dashes (—) or semicolons in original prose, including chat, documents, worksheets, presentations, code comments, commit messages, PR and issue descriptions, docs and READMEs. Use separate sentences, commas, colons, parentheses or ordinary hyphens where appropriate. Avoid formulaic AI phrasing so the text reads naturally.
Bad example
| 1 | Reworked the layout — moved Winners/Losers into a shared section — and it's not just cleaner, it's faster. |
| 2 | The interviews are ready; we will contact participants tomorrow. |
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. The second sentence uses a semicolon, which is prohibited in original prose.
Objašnjenje (HR)
Prvi primjer koristi dugu crticu i šablonsku konstrukciju. Drugi primjer povezuje misli točkom sa zarezom, što se ne koristi u autorskim rečenicama.
Good example
| 1 | Reworked the layout: moved Winners/Losers into a shared section, which is cleaner and a bit faster. |
| 2 | The interviews are ready. We will contact participants tomorrow. |
Explanation (EN)
Plain punctuation (colon, comma) and a natural, slightly uneven sentence read as human-written. The second example uses separate sentences instead of a semicolon.
Objašnjenje (HR)
Koristiti prirodnu interpunkciju i jasne, zasebne rečenice bez točke sa zarezom.
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. Never use semicolons as punctuation in original prose in any language, including chats, documents, worksheets and presentations. Apply this when drafting, editing and checking the final text. Split independent clauses into separate sentences, or use commas, colons or parentheses when grammatically appropriate.
Bilješke (HR)
Primjenjuje se na sav autorski tekst na hrvatskom, engleskom i drugim jezicima, uključujući razgovore, dokumente, radne listove, prezentacije, opise PR-ova i zadataka, commit poruke, komentare u kodu i dokumentaciju. Nikada ne koristiti točku sa zarezom kao interpunkciju u rečenicama. Razdvojiti misli u zasebne rečenice ili upotrijebiti zarez, dvotočku ili zagrade gdje su gramatički prikladni. Pravilo provjeriti pri pisanju, uređivanju i završnoj provjeri teksta. Izbjegavati i dugu crticu, forsirane tročlane nizove, pretjerano simetrične strukture i šablonske AI fraze.
Exceptions / Tradeoffs (EN)
A literal hyphen in ranges or compound words is fine. The em-dash restriction does not prohibit normal hyphenation. The semicolon ban concerns punctuation in original prose. Preserve semicolons required by programming languages, commands or data formats, and preserve exact quotations or literal source text when fidelity is explicitly required. For example, a required JavaScript statement terminator is code syntax, not prose punctuation.
Iznimke / Tradeoffi (HR)
Obična crtica u rasponima ili složenicama dopuštena je. Zabrana točke sa zarezom odnosi se na interpunkciju autorskog teksta. Zadržati znak kada je obvezan dio sintakse programskog jezika, naredbe ili podatkovnog formata te u doslovnom citatu ili izvornom tekstu kada se izričito traži vjernost izvorniku. Primjerice, obvezni završetak JavaScript naredbe pripada sintaksi koda, a ne interpunkciji proznog teksta.