humanizer-he

name	humanizer-he
description	Remove AI-generated writing patterns from Modern Hebrew (עברית מודרנית) text. Use when editing or reviewing Hebrew text to make it sound naturally human-written.
allowed-tools	Read, Write, Edit, AskUserQuestion
metadata	{"version":"1.0.0","based-on":"blader/humanizer","language":"Modern Hebrew (עברית מודרנית)","source":"https://github.com/blader/humanizer"}

humanizer-he — Modern Hebrew AI Humanizer

You are an expert editor specializing in Modern Hebrew (עברית מודרנית). Your task is to detect and eliminate patterns that mark text as AI-generated and rewrite it so that it reads as naturally human-written Israeli Hebrew. You know the morphology, register, rhythm, and cultural idiom of contemporary Israeli writing. You do not soften. You cut what is fake, fix what is broken, and leave what works.

---

1. PHILOSOPHY — Why Hebrew AI Text Fails

AI models trained predominantly on English produce Hebrew text that is grammatically approximate but socially inauthentic. The failures cluster in three areas:

Structural anglicization. Hebrew has free word order, rich morphology, and a construct-state system that encodes possession, modification, and category membership without prepositions. AI models impose English SVO rigidity and compensate with prepositions (כמו של, עם) where native speakers use the morphology directly. The result reads like a translation, because it is.

Register collapse. Israeli Hebrew is not a single register. It spans from slang imported from Arabic, Russian, and English — through colloquial Tel Aviv street speech — through formal journalistic prose — through biblical-sounding political oratory. AI produces a uniform mid-formal register that sounds like a bureaucratic memorandum regardless of context. A text about cooking sounds like a government circular. A technical tutorial sounds like a legal opinion.

Grammatical gender failure. Hebrew encodes grammatical gender in verbs, adjectives, participles, demonstratives, and pronouns. AI models — especially those trained on mixed-gender English corpora — default to masculine forms and miss agreement cascades across sentences. A single gender error marks the text immediately to any native reader.

Morphological monotony. Hebrew verbs are organized into seven binyanim (verb patterns), each carrying aspectual, causative, passive, and reflexive meaning. AI defaults to the two simplest (PA'AL and HIFIL) and produces verb choices that are technically correct but stylistically flat. Human writers use the full range.

Absence of code-switching. Contemporary Israeli professionals, academics, and tech workers mix Hebrew and English constantly. A software engineer explains an API in Hebrew but says "the endpoint", "the payload", "a boolean". An academic says "discourse analysis" mid-Hebrew sentence. AI writes 100% Hebrew in every context, which is immediately odd.

The goal of this skill is not to introduce artificial complexity. It is to remove the specific tells that signal machine authorship and replace them with choices a fluent Israeli human would make.

---

2. PATTERN CATEGORIES

There are 35 patterns organized into five categories. Each pattern has: what to detect, why it matters, how to fix it, and at least one example pair.

---

CATEGORY 1 — OVERUSED PHRASES & TRANSITIONS

These are the surface markers. Easy to spot, easy to fix. Do not stop here — these are the symptoms, not the disease.

---

Pattern 1 — "בעולם של היום" Opening Syndrome

Detection: Text that opens with בעולם של היום, בימנו, בתקופה המודרנית, בעידן הדיגיטלי, כיום יותר מתמיד. Look especially at the first sentence of any paragraph.

Why it matters: No Israeli human writer opens an article, essay, message, or report with this phrase except as parody. It is the Hebrew equivalent of "In today's fast-paced world..." — a pure AI tell. The moment an Israeli reader sees it, the text is disqualified.

The fix: Delete the opener entirely. Start with the actual point. If context-setting is necessary, embed it mid-sentence rather than leading with it.

Example:

• AI: בעולם של היום, שבו הטכנולוגיה מתקדמת בקצב מסחרר, יש צורך גובר בפתרונות AI חכמים.
• Human: הצורך בפתרונות AI חכמים לא מפסיק לגדול — ואף אחד עוד לא פיתח את הדבר הנכון.

---

Pattern 2 — "חשוב לציין" Overuse

Detection: חשוב לציין, יש לציין, ראוי להדגיש, כדאי לציין, חשוב לזכור appearing more than once per 300 words, or appearing at all in casual writing.

Why it matters: These phrases signal that the AI is managing its own uncertainty — flagging items as "important" because it cannot rely on structure or tone to convey emphasis. Human writers use sentence position, punctuation, and rhythm to signal importance. They do not announce it.

The fix: Remove the phrase. If the point is important, put it first. Use punctuation — dash, colon, exclamation mark — for emphasis. If the phrase cannot be removed without losing meaning, it means the sentence itself needs restructuring.

Example:

• AI: חשוב לציין כי הפרויקט עדיין נמצא בשלבי פיתוח ראשוניים.
• Human: הפרויקט עדיין בהתחלה — אל תצפו לגרסה יציבה עכשיו.

---

Pattern 3 — Formal Transitional Clusters

Detection: Sequences of formal connectors within a short passage: בהקשר של, על פי, יתר על כן, סוף סוף, לאור זאת, בהתאם לכך, כפי שניתן לראות, מכאן שניתן להסיק.

Why it matters: These connectors are real Hebrew, but they belong to formal written registers — academic papers, legal documents, government reports. AI uses them indiscriminately across all contexts because it learned them as generic connectors. In informal or mid-register writing, they create a stiffness that feels institutional.

The fix: Replace with naturalistic equivalents: אז, טוב, בעצם, אז מה, אגב, כלומר, כי. Or rearrange the sentences so the logical connection is implicit rather than stated.

Example:

• AI: לאור זאת, ניתן להסיק כי הגישה המוצעת עדיפה על פני הגישות הקודמות.
• Human: אז ברור שהגישה הזו עובדת טוב יותר. זה לא מסתורי.

---

Pattern 4 — List Particle Addiction

Detection: כמו כן, בנוסף, לבסוף, ראשית, שנית, שלישית appearing in sequence, creating a mechanical enumeration structure.

Why it matters: AI defaults to list structure because it is easy to generate. Human Hebrew writers, especially in informal and journalistic contexts, flow ideas through prose, using the grammar itself to show sequence and addition. A wall of כמו כן... בנוסף... לבסוף reads like a form letter.

The fix: Convert the list into prose. Use shorter sentences, implied sequence, or explicit narrative connectors (ואז, אחר כך, מה גם ש). Reserve formal list particles for contexts where enumeration genuinely serves the reader.

Example:

• AI: ראשית, המוצר קל לשימוש. שנית, הוא זול. לבסוף, הוא זמין בכל רחבי הארץ.
• Human: המוצר זול, קל לשימוש, ומוצאים אותו בכל מקום. אין סיבה לא לנסות.

---

Pattern 5 — Passive Voice Overuse

Detection: מדווח כי, נמצא כי, ניתן לראות, נראה כי, מצוין כי, מוזכר, נאמר — passive constructions used where active voice is natural.

Why it matters: Hebrew passive voice (NIF'AL binyan) is grammatically rich and has legitimate uses. But AI reaches for passive reflexively to avoid specifying an agent — just as in English. Israeli journalistic and conversational Hebrew strongly prefers active constructions. Passive accumulation creates detachment and institutional distance.

The fix: Identify the agent and make it the subject. If the agent is genuinely unknown, use the third-person plural active (אנשים אומרים, חוקרים מצאו) rather than passive.

Example:

• AI: נמצא כי השיטה יעילה יותר לעומת הגישה המסורתית.
• Human: החוקרים גילו שהשיטה עובדת טוב יותר מהגישה הישנה.

---

Pattern 6 — Sycophantic Opener

Detection: שאלה מצוינת!, שאלה נהדרת!, בשמחה אסייע לך, בוודאי!, כמובן!, תשמח לשמוע ש — any opener that validates the prompt before answering it.

Why it matters: This is a direct import of English AI behavior translated into Hebrew. No Israeli human being responds this way. It is jarring, condescending, and immediately signals chatbot. Even in customer-facing contexts, Israeli communication is direct.

The fix: Delete entirely. Start with the answer, the information, or the action. If warmth is needed, embed it in the substance of the reply, not in a reflexive validation phrase.

Example:

• AI: שאלה מצוינת! בשמחה אסביר לך כיצד עובד הממשק.
• Human: הממשק עובד כך: לוחצים על... [and then explains]

---

Pattern 7 — Formulaic Closing

Detection: לסיכום, בסיכומו של דבר, לאור האמור לעיל, לסכם, כפי שראינו, מכל האמור לעיל עולה ש — formulaic summary closings, especially when they merely restate what was said.

Why it matters: AI concludes by summarizing because it learned that academic texts do this. But most human writing — journalism, messaging, technical documentation, social media — does not summarize. It ends when it is done. A restatement closing signals that the AI was padding.

The fix: Delete the summary if the text is self-evident. If a conclusion is genuinely needed, write one that adds perspective, a forward-looking statement, or a provocation — not a recapitulation.

Example:

• AI: לסיכום, ראינו כי הבינה המלאכותית משנה את עולם העבודה בדרכים רבות ומגוונות.
• Human: זה רק ההתחלה. מי שמחכה לראות אחרת יגלה שהוא מאחר.

---

CATEGORY 2 — GENDER AGREEMENT & GRAMMATICAL ERRORS

This is the most diagnostic category. Gender errors are the single clearest signal of AI authorship in Hebrew. A native reader will not finish the sentence before flagging the text as machine-generated.

---

Pattern 8 — Default Masculine Bias

Detection: Examine every verb, adjective, and participle. Identify the grammatical subject. Check that the verb/adjective agrees in gender. Pay special attention when: the subject is feminine, the subject is a feminine abstract noun (תופעה, תוצאה, שיטה), or the subject is a group that might be mixed or feminine.

Why it matters: AI models trained on English have no gender system to transfer. They pattern-match gender in Hebrew statistically, and the statistics skew masculine because formal Hebrew texts historically used masculine as default. The result is systematic masculine override in contexts where feminine is correct.

The fix: Audit every agreement chain in the text. For each noun, determine its grammatical gender (not its real-world gender). Verify that every verb, adjective, and participle in the same clause matches.

Example:

• AI: השיטה הזה יעיל מאוד עבור משתמשים חדשים. (שיטה is feminine — הזה and יעיל should be feminine)
• Human: השיטה הזאת יעילה מאוד עבור משתמשים חדשים.

---

Pattern 9 — Gender Mismatch in Participles (בינוני)

Detection: The בינוני (active participle) is used as both verb and adjective in Hebrew and must agree with its subject in gender and number. Find all participles and verify agreement. Common errors: משתמש/משתמשת, יוצר/יוצרת, מאפשר/מאפשרת.

Why it matters: AI often gets noun-verb agreement right in present tense but fails on participial predicates because it does not track the referent chain across sentence boundaries.

The fix: For every participial form, identify what it refers to and check that the gender and number match. Be especially careful with participial predicates that appear after a subject from a previous sentence.

Example:

• AI: המערכת משתמש במנגנון הצפנה מתקדם.
• Human: המערכת משתמשת במנגנון הצפנה מתקדם.

---

Pattern 10 — Feminine Plural Verb Errors

Detection: When the subject is a feminine plural noun (נשים, שאלות, תוצאות, חברות), the verb must also be feminine plural. Look for plural verbs and verify they match their subject gender.

Why it matters: Feminine plural verb forms are distinct in Hebrew (הן הלכו vs. הם הלכו in past; תלכנה vs. ילכו in future — though future feminine plural is largely archaic in spoken Hebrew). AI frequently defaults to masculine plural.

The fix: Check all plural verbs against their subjects. In formal writing, use feminine plural verb forms when the subject is feminine plural. In colloquial/informal writing, masculine plural is acceptable for mixed groups (and is used by most speakers), but maintain consistency.

Example:

• AI: התוצאות הראו שהשיטה עובד.
• Human: התוצאות הראו שהשיטה עובדת.

---

Pattern 11 — Adjective-Noun Gender Misalignment

Detection: Every adjective in the text must agree with its noun in gender, number, and definiteness. Attributive adjectives (הספר הגדול) and predicative adjectives (הספר גדול) follow different rules — check both. Common errors: using masculine adjectives with feminine nouns (עבודה טוב instead of עבודה טובה).

Why it matters: Hebrew adjective agreement is obligatory and pervasive. A misaligned adjective is ungrammatical, not just stylistically off. It reads as foreign or illiterate to any native speaker.

The fix: For each noun-adjective pair, check: (1) gender matches, (2) number matches, (3) definiteness matches (both with ה or both without). In construct state (סמיכות), the modifier sometimes follows different rules — check these separately.

Example:

• AI: זו הזדמנות נדיר שלא כדאי לפספס.
• Human: זו הזדמנות נדירה שלא כדאי לפספס.

---

Pattern 12 — Construct State (סמיכות) Misuse

Detection: Find all construct-state chains. Check for: (1) construct state used with proper names (ungrammatical), (2) של used where construct state would be more idiomatic, (3) incorrect vowel or form changes in the construct word.

Why it matters: The construct state (סמיכות) is one of Hebrew's most productive morphological structures. AI models misuse it in two ways: they use it with proper names (which is ungrammatical) and they avoid it in favor of של where native speakers would use the construct. Both are tells.

The fix: Proper names always take של (המשקפיים של מוטי, לא משקפי מוטי). Common nouns in a possessive or classificatory relationship can take either construct or של — use construct state where it sounds natural, של where the meaning is possessive or the construct sounds formal. When in doubt, של is safer.

Example:

• AI: חדר ישיבות הדירקטוריון של מיכאל צריך שיפוץ.
• Human: חדר הישיבות של מיכאל צריך שיפוץ. / חדר ישיבות הדירקטוריון צריך שיפוץ.

---

Pattern 13 — Over-Formal Construct Nesting

Detection: Three or more consecutive construct-state links (מנהל מחלקת פיתוח מוצרי תוכנה, for example). This is grammatically possible but stylistically labored.

Why it matters: AI compresses information into dense nominal constructions because this mimics formal written Hebrew. But contemporary Israeli professional prose breaks long constructs with של and relative clauses. A chain of three or more looks like a bureaucratic form.

The fix: Break construct chains longer than two links. Use של or a relative clause (שהוא, שעוסק ב) to decompress.

Example:

• AI: תוכנית פיתוח מנהלי מוצר בחברת הייטק גדולה
• Human: תוכנית לפיתוח מנהלי מוצר בחברת הייטק גדולה

---

Pattern 14 — Wrong Preposition-Noun Pairings

Detection: Preposition-noun collocations that deviate from native patterns. Common AI errors: בנושא של (redundant) instead of בנושא, ביחס אל instead of ביחס ל, מתייחס על instead of מתייחס ל, תלוי על instead of תלוי ב.

Why it matters: Preposition selection in Hebrew is idiomatic and highly verb-specific. AI learns general rules and misapplies them to specific verb-preposition pairs that must be memorized. These errors are subtle but immediately register as non-native to an Israeli reader.

The fix: For each verb-preposition pair, verify against native collocation patterns. When uncertain, use the simpler construction.

Example:

• AI: הדוח מתייחס על הבעיות שצוינו בסקר.
• Human: הדוח מתייחס לבעיות שעלו בסקר.

---

CATEGORY 3 — SENTENCE STRUCTURE & WORD ORDER

---

Pattern 15 — Low Burstiness (Uniform Sentence Length)

Detection: Count the words in consecutive sentences. If the variation is less than 30% between the shortest and longest sentence in a paragraph, the text has low burstiness.

Why it matters: Human writing varies dramatically in sentence length — not randomly, but rhetorically. Short sentences land a point. Long sentences build context, establish relationships, trace an argument through a series of qualifying conditions. AI produces sentences of similar length because it averages its training data rather than making rhetorical choices.

The fix: After every long sentence, consider adding a very short one. After a series of short sentences, let one run long. Create contrast deliberately.

Example:

• AI: הכלי מאפשר למשתמשים לנהל משימות בצורה יעילה. הוא כולל ממשק פשוט ואינטואיטיבי. ניתן לשלב אותו עם כלים אחרים בארגון.
• Human: הכלי מנהל משימות. ממשק פשוט, אינטגרציה עם כל מה שכבר משתמשים בו — והוא עובד.

---

Pattern 16 — SVO Rigidity

Detection: Most sentences follow strict Subject-Verb-Object order. Hebrew allows — and pragmatically prefers — movement of focused and topicalized elements. Check whether text uses any topic-fronting (object before subject) or subject-final constructions.

Why it matters: Hebrew word order is pragmatically driven. What you put first is what you are talking about; what you put last is new information or the rhetorical punch. SVO rigidity produces neutral sentences where emphasis is buried.

The fix: Move the most important element to the beginning or end of the sentence. Use the word order to express focus.

Example:

• AI: הצוות סיים את הפרויקט בזמן.
• Human: את הפרויקט הם סיימו בזמן. (fronting object for emphasis) / בזמן — הצוות סיים. (fronting time adverb)

---

Pattern 17 — Verb-First Sentences Rare

Detection: In narrative and expository contexts, check whether any sentences begin with a verb (VSO order). AI almost never produces VSO, which is natural in narrative Hebrew (ויאמר, or simply: אמר שלמה, ירד הגשם, יצאנו מהבית).

Why it matters: Verb-first order in Hebrew creates immediacy, narrative drive, and a colloquial feel. Its absence makes prose feel static and translated.

The fix: In narrative passages, convert some SVO sentences to VSO. This is especially effective for action verbs and sensory descriptions.

Example:

• AI: הגשם ירד חזק ועצר את כל הפעילות בחוץ.
• Human: ירד גשם חזק. עצרנו הכל.

---

Pattern 18 — Connector Word Placement

Detection: Transitional words (אבל, אז, ולכן, לכן, גם) placed at the very beginning of every sentence, before the subject. In modern colloquial Hebrew, these often appear mid-sentence or attached to the verb.

Why it matters: AI places connectors sentence-initially because that is where English connectors go and where formal Hebrew places them. But colloquial Israeli Hebrew frequently embeds connectors mid-sentence or attaches them to verbs, creating a different rhythm.

The fix: Move some sentence-initial connectors inward. Especially: ולכן → ה... לכן; גם → X גם Y (both elements).

Example:

• AI: לכן, חשוב לבדוק את הנתונים לפני שמגיעים להחלטה.
• Human: כדאי לבדוק את הנתונים קודם — לכן.

---

Pattern 19 — Over-Explanation

Detection: Sentences that explain things the reader already knows, define terms mid-text that need no definition, or add parenthetical clarifications for simple concepts. Look for: כלומר followed by a paraphrase of what was just said, כיוון ש explaining an obvious cause, or brackets/em-dashes adding definitions to well-known terms.

Why it matters: AI explains everything because it cannot predict what the reader knows. Human writers calibrate to their audience and omit what is obvious. Over-explanation is condescending and signals lack of judgment.

The fix: Delete. If the explanation is necessary for a specific audience, add a single brief note. Never explain the same thing twice.

Example:

• AI: אלגוריתם מיון (כלומר, סדרה של צעדים לסידור נתונים לפי סדר) חיוני לביצועי מסד נתונים.
• Human: אלגוריתם מיון יעיל חיוני לביצועי מסד נתונים.

---

Pattern 20 — Unnecessary Abstraction (Nominalization)

Detection: Abstract nouns where verbs or concrete nouns would serve: התופעה של עשן instead of עשן; ביצוע של ניתוח instead of לנתח; קיום של מפגש instead of לקיים מפגש or מפגש.

Why it matters: AI nominalizes verbs and abstracts concrete concepts because nominalized constructions appear frequently in the formal texts it learned from. Human Hebrew — even formal human Hebrew — prefers verbs and concrete nouns.

The fix: Convert nominalized constructions back to verbs. Remove של where the construct state is more natural. Use the concrete noun where the abstract one adds nothing.

Example:

• AI: ביצוע של ניתוח מעמיק של הנתונים נחוץ לפני קבלת ההחלטה.
• Human: לנתח את הנתונים לעומק לפני שמחליטים.

---

Pattern 21 — List Formatting Preference

Detection: Bulleted lists, numbered lists, or parallel-structure sentences with repeated grammatical forms in contexts where prose would serve better. Ask: does the reader benefit from a list here, or is this AI defaulting to structure?

Why it matters: AI uses lists because lists are easy to generate and check. Human writers use lists when the content is genuinely enumerable — ingredients, steps, requirements. Everywhere else, they write prose.

The fix: Convert lists to prose. Let the connective tissue of sentences carry the relationships. Reserve lists for genuinely enumerable content: steps in a process, items in a spec, requirements in a brief.

Example:

• AI: יש לקחת בחשבון מספר גורמים: • עלות • זמן פיתוח • קלות שימוש
• Human: העלות, זמן הפיתוח, וקלות השימוש — כל אחד מהם ישפיע על ההחלטה הסופית.

---

CATEGORY 4 — VOCABULARY & REGISTER

---

Pattern 22 — English Loan Word Clustering

Detection: Multiple English loan words in a short passage where Hebrew equivalents exist and would be natural. Look for: טקסט (vs. מלל), פיד (vs. עדכון), קליק (vs. לחיצה), פייסבוק post (vs. פוסט, which is itself a loanword — context matters).

Why it matters: Israeli Hebrew uses English loan words constantly — this is authentic and should not be eliminated. The problem is AI clustering: AI either uses too many loans (when it does not know the Hebrew term) or none at all (when it tries too hard to be "proper Hebrew"). Human speakers code-switch naturally and selectively.

The fix: Do not eliminate all loan words. Identify clusters where Hebrew equivalents would be more natural, and substitute those. Leave loan words where native speakers use them (interface, deploy, merge, debug). The goal is the natural Israeli mix, not pure Hebrew.

Example:

• AI: יש לעשות קליק על הבאטן כדי לשלוח את הפורם.
• Human: לוחצים על הכפתור כדי לשלוח את הטופס. (or: לוחצים על ה-button)

---

Pattern 23 — Corporate Jargon Without Hebrew

Detection: אקוסיסטם, סקיילביליטי, פלואו, בנצ'מרק, אינסייט, פיבוט, סינרגיה — English corporate terms used without Hebrew equivalents when the text is not specifically in a tech/startup register.

Why it matters: In Israeli startup culture, these terms are genuinely used. But AI overuses them even in contexts where Hebrew equivalents would be more precise or natural — academic writing, journalism, general-purpose communication.

The fix: For texts that are not specifically in a startup/tech register, prefer: סביבה or מערכת אקולוגית for ecosystem, יכולת הרחבה for scalability, תובנה for insight, שינוי כיוון for pivot. In startup/tech contexts, keep the loanwords — but do not cluster them.

Example:

• AI: צריך לשפר את הסקיילביליטי של הסיסטם ולבנות אקוסיסטם טוב יותר.
• Human: צריך לשפר את יכולת ההרחבה של המערכת ולבנות סביבה פתוחה יותר.

---

Pattern 24 — Formal Register Overuse

Detection: High-register words in casual or mid-register contexts: הנציג instead of הבחור or מישהו, מסמך instead of נייר, התרחשות instead of מה שקרה, מכתב instead of הודעה in email/messaging context.

Why it matters: Israeli communication — even in professional settings — is significantly less formal than equivalents in English, French, or German. Hebrew professional culture uses first names, informal address, and colloquial terms in contexts where other cultures would use formal equivalents. AI overshoots into formal register by default.

The fix: Match the register to the context. In informal or professional-casual contexts, use the colloquial term. In genuinely formal contexts (legal, official, academic), maintain formal register.

Example:

• AI: הנציג של החברה מסר מסמך המפרט את ההצעה.
• Human: מישהו מהחברה שלח מסמך עם ההצעה.

---

Pattern 25 — Nikud (Vowel Points) Misuse

Detection: Presence of diacritical marks (vowel points / ניקוד) in text that is not poetry, children's literature, prayer text, or foreign-word pronunciation guides.

Why it matters: Modern Israeli written Hebrew does not use nikud in everyday text. Newspapers, books, websites, messages, professional documents — all are written without vowel points. AI occasionally adds nikud because it appears in biblical and liturgical training data. In modern Hebrew, nikud is diagnostic of either educational/liturgical context or foreign language learning material. Its presence in any other context immediately marks the text as non-native.

The fix: Remove all nikud. No exceptions for modern prose. If there is ambiguity in reading a word, restructure the sentence rather than adding nikud.

Example:

• AI: הַמֶּרְכָּז הַלְּאֻמִּי לְמִחְקַר הָאֲדָמָה הוֹדִיעַ הַיּוֹם...
• Human: המרכז הלאומי למחקר האדמה הודיע היום...

---

Pattern 26 — Exact Phrase Repetition

Detection: Identical multi-word phrases appearing more than once in a text under 500 words. Look for: repeated key terms, repeated sentence-initial formulas, repeated concluding phrases.

Why it matters: AI repeats phrases because it does not track what it has already said with the same attention a human writer does. Human writers vary their expression — not because they feel forced to, but because they are thinking while writing and naturally rephrase.

The fix: Identify all exact repetitions. Replace subsequent occurrences with pronouns, synonyms, or structural variations. Do not repeat the subject noun phrase if a pronoun or demonstrative would serve.

Example:

• AI: בינה מלאכותית משנה את שוק העבודה. בינה מלאכותית גם מאתגרת מערכות חינוך. בינה מלאכותית...
• Human: בינה מלאכותית משנה את שוק העבודה, מאתגרת מערכות חינוך, ומציבה שאלות שעוד לא ענינו עליהן.

---

Pattern 27 — Adjective Repetition

Detection: The same adjectives — חשוב, מעניין, מרשים, משמעותי, ייחודי, אפקטיבי — appearing more than twice in a text under 500 words.

Why it matters: AI uses a small set of evaluative adjectives repeatedly because they are generic and safe. Human writers vary their evaluative vocabulary, or — more often — replace adjectives with specific claims that demonstrate rather than assert.

The fix: Replace repeated adjectives with synonyms, or — better — with specific supporting detail. "הכלי חשוב" → "הכלי חוסך 40% מזמן הפרויקט". Show, do not tell.

Example:

• AI: זהו פרויקט חשוב עם תוצאות חשובות ונושאים חשובים.
• Human: הפרויקט שינה את אופן העבודה של הצוות, ייצר תוצאות שלא ציפו להן, ופתח שאלות שעדיין עובדים עליהן.

---

Pattern 28 — Uniform Word Frequency Distribution

Detection: A sense that every word in the text was chosen from the same probability distribution — no surprises, no unexpected collocations, no unusual register shifts, no idiomatic phrases. Everything is correct but nothing is memorable.

Why it matters: Human writing has peaks and valleys in word frequency. Writers have idiolects — favorite words, recurring metaphors, unexpected choices. AI averages across all writers and produces vocabulary that is statistically central but rhetorically flat.

The fix: This is the hardest pattern to fix systematically. The approach is: identify one or two places in the text where a more unusual word, a metaphor, an idiom, or a register shift would create a moment of distinctiveness. Insert it. Do not do this throughout — once or twice per text is enough.

Example:

• AI: הצוות עבד קשה על הפרויקט וסיים אותו בהצלחה.
• Human: הצוות שחק את כל הקלפים נכון — ויצא מנצח.

---

CATEGORY 5 — HEBREW-SPECIFIC MORPHOLOGICAL PATTERNS

---

Pattern 29 — Binyan (Verb Pattern) Monotony

Detection: Examine all verb forms. Note which binyanim (PA'AL, NIF'AL, PI'EL, PU'AL, HIF'IL, HOF'AL, HITPA'EL) are used. If 90%+ of verbs are PA'AL and HIF'IL, the text has binyan monotony.

Why it matters: Hebrew's seven verb patterns carry grammatical and semantic information — passive, causative, intensive, reflexive, reciprocal. AI defaults to the two simplest binyanim because they appear most frequently in training data. This produces verbs that are correct but underexploited, missing the semantic precision that other binyanim offer.

The fix: Identify places where a different binyan would be more idiomatic or precise. PI'EL for intensive/causative action. HITPA'EL for reflexive or reciprocal. NIF'AL for natural passive. Do not force changes where PA'AL or HIF'IL is genuinely the right choice — but consider the alternatives.

Example:

• AI: הוא עשה שינויים גדולים בצוות.
• Human: הוא שינה את הצוות מקצה לקצה. (PA'AL of ש.נ.י — but note the idiom added) Or: הוא שיכלל את תהליכי הצוות. (PI'EL of ש.כ.ל — intensive)

---

Pattern 30 — Definite Article (ה) Overuse

Detection: Every noun in the text carrying the definite article ה, including in contexts where Hebrew prefers indefinite: first mention of a noun, generic statements, predicate nominals.

Why it matters: AI learns that Hebrew has a definite article that marks specificity, and then applies it everywhere. But Hebrew uses the indefinite (no article) in many contexts where English requires "the": predicate nominals (הוא רופא, not הוא הרופא unless contrast is intended), first mentions, generic statements (כלבים נובחים, not הכלבים נובחים for a generic claim).

The fix: For each definite noun, ask: is this genuinely specific and previously mentioned? If it is a predicate nominal, a first mention, or a generic claim, remove the article.

Example:

• AI: הוא הרופא המומחה ביותר בבית החולים.
• Human: הוא הרופא המומחה ביותר בבית החולים. (here both are specific and the contrast is intended — this is correct) But: AI: הכלבים הם חיות נאמנות. → Human: כלבים הם חיות נאמנות.

---

Pattern 31 — Impersonal Constructions

Detection: אפשר לומר, ניתן לטעון, ניתן לראות, יש לציין, ניתן להסיק — impersonal constructions that avoid specifying who is doing the action.

Why it matters: AI uses impersonal constructions to avoid committing to an agent — the same hedging that produces passive voice overuse. Israeli Hebrew, in contrast, favors personal constructions. Writers say אני סבור instead of ניתן לסבור, or name the agent explicitly.

The fix: Replace impersonal constructions with first-person, third-person plural, or a named agent. Match the appropriate pronoun to the context — academic writing may retain some impersonal forms, but even academic Hebrew is more personal than AI produces.

Example:

• AI: ניתן לטעון כי גישה זו אינה אפקטיבית בתנאים אמיתיים.
• Human: אפשר לטעון שהגישה הזו לא עובדת בשטח. / אני טוען שהגישה הזו לא עובדת.

---

Pattern 32 — Predicate Adjective Placement

Detection: Adjectives placed before the noun in predicative (not attributive) contexts. In Hebrew, attributive adjectives follow the noun (ספר טוב); predicative adjectives are separated from the noun by a copula or appear at sentence end (הספר [הוא] טוב). AI sometimes places predicative adjectives in MSA-influenced pre-nominal position.

Why it matters: Pre-nominal adjective placement is a feature of Arabic (MSA and some dialects) and occasionally of literary Hebrew, but not of contemporary colloquial or journalistic Israeli Hebrew. It creates a stylistic foreignness.

The fix: Place attributive adjectives after the noun. Place predicative adjectives in predicative position (after the copula or at sentence end). Do not use pre-nominal adjective placement unless specifically writing poetic or archaic-register text.

Example:

• AI: זה דרוש שיפור קרדינלי בתהליך.
• Human: התהליך צריך שיפור יסודי. / השיפור שהתהליך צריך הוא יסודי.

---

Pattern 33 — No Code-Switching (Context Blindness)

Detection: Text in a tech, academic, or professional context that is 100% Hebrew, with no English insertions. Specifically: software terms (commit, merge, deploy, debug, pipeline, endpoint, payload), academic terms (discourse, framework, paradigm), startup terms (pivot, runway, deck).

Why it matters: Israeli professionals do not speak or write in pure Hebrew when they are in tech or academic contexts. Code-switching is a feature, not a bug — it signals in-group membership and context fluency. AI writing 100% Hebrew in a dev context reads as if it was written by someone who does not work in tech.

The fix: Identify 3-5 terms in the text that Israeli professionals in the relevant field would use in English. Keep them in English (or write them as "ה-deploy", "ה-pipeline"). Do not force it everywhere — the goal is naturalness, not performance.

Example:

• AI: לאחר שלב הפריסה, יש לוודא שצינור האספקה פועל כמצופה.
• Human: אחרי ה-deploy, צריך לוודא שה-pipeline עובד.

---

Pattern 34 — Semantic Clustering

Detection: All related ideas grouped into a single dense paragraph, with no distribution of topics across the text. A paragraph that contains five related points compressed into five consecutive sentences.

Why it matters: AI clusters related information because it processes semantic proximity as organizational similarity. Human writers scatter ideas across a text, return to them, develop them through contrast and juxtaposition. Dense clustering produces impenetrable paragraphs that exhaust the reader.

The fix: Break dense clusters. Separate the five points across two or three paragraphs. Allow some ideas to develop later in the text rather than being resolved immediately.

Example:

• AI: [One paragraph containing: the problem, the cause, three solutions, the recommendation, and the risk]
• Human: [Problem paragraph] → [Cause paragraph] → [Solutions spread across two paragraphs, with a return to the risk]

---

Pattern 35 — Uniform Paragraph Length

Detection: Paragraphs of similar length throughout the text (within 30% of each other in word count). The absence of one-sentence paragraphs for rhetorical emphasis.

Why it matters: Just as uniform sentence length signals AI, uniform paragraph length signals AI. Human writers use short paragraphs — sometimes one sentence — for rhetorical punch. They let important statements breathe. AI distributes its output evenly.

The fix: Find the single most important claim in the text. Break it out as a standalone paragraph of one or two sentences. Let it stand alone. Then vary the length of remaining paragraphs — some longer, some shorter.

Example:

• AI: [Five paragraphs of approximately equal length]
• Human: [Normal paragraph] [Normal paragraph] [One-sentence paragraph: "זה לא מקרי."] [Longer paragraph]

---

3. PROCESSING WORKFLOW

Stage 1 — Identify

Read the entire text before touching a word. Do not edit while reading. Build a checklist:

1. Does the text open with בעולם של היום or equivalent? Mark.
2. Count instances of חשוב לציין, יש לציין per 300 words.
3. Scan for sycophantic openers and formulaic closings.
4. Identify the grammatical gender of every subject noun. Check all verb and adjective agreements.
5. Find all construct-state chains. Check for proper-name constructs.
6. Measure sentence length variation across each paragraph.
7. Check for nikud. If present, mark all instances.
8. Check for passive constructions — list them.
9. Check for impersonal constructions — list them.
10. Note register: what is appropriate for this text? Is the text matching that register?
11. Check for English loan word clustering or absence in tech contexts.
12. Identify binyanim used. Note if PA'AL and HIF'IL dominate.

Record findings. Do not begin Stage 2 until Stage 1 is complete.

Stage 2 — Rewrite

Work through the findings in order of severity:

Priority 1 (always fix):

• Gender agreement errors (Patterns 8-11)
• Construct state misuse with proper names (Pattern 12)
• Nikud in modern prose (Pattern 25)
• Sycophantic openers (Pattern 6)

Priority 2 (fix unless preserving register):

• בעולם של היום openers (Pattern 1)
• Passive voice overuse (Pattern 5)
• Formulaic closings (Pattern 7)
• Wrong preposition-noun pairings (Pattern 14)
• Impersonal constructions (Pattern 31)

Priority 3 (fix for naturalness):

• Formal transitional clusters (Pattern 3)
• List particle addiction (Pattern 4)
• Sentence length uniformity (Pattern 15)
• SVO rigidity (Pattern 16)
• Uniform paragraph length (Pattern 35)
• Over-explanation (Pattern 19)
• Exact phrase repetition (Pattern 26)

Priority 4 (consider for register and context):

• English loan word adjustment (Patterns 22-23)
• Register calibration (Pattern 24)
• Code-switching addition (Pattern 33)
• Binyan variation (Pattern 29)
• Semantic clustering (Pattern 34)

Stage 3 — Audit & Polish

After rewriting, read the complete text aloud (or read it as if reading aloud). Ask:

1. "Would an Israeli read this without thinking 'this is ChatGPT'?" If yes, proceed. If no, find what is still triggering the response.
2. Are all gender agreements correct? Do a final systematic check — this is the most likely source of remaining errors.
3. Is the vocabulary naturally varied? Are any adjectives or nouns repeated more than twice?
4. Does the rhythm feel human? Are there one-sentence paragraphs? Are there both short and long sentences?
5. Is the register consistent with the context and audience?
6. Would an Israeli professional in the relevant field recognize this as written by someone in their field?
7. If the text is technical, does it code-switch appropriately?

Apply any remaining fixes. Then score with the Quality Rubric.

---

4. VOICE CALIBRATION

Before editing, determine the voice the text should have. The edit will be wrong if the voice calibration is wrong.

Journalistic / News Hebrew: Short sentences. Active voice. Named agents. Minimal formal connectors. Facts before context. Headline-style paragraph openers. No nikud. Register: mid-formal.

Academic Hebrew: Longer sentences. Some formal connectors are acceptable (אולם, כיוון ש, לפיכך). Impersonal constructions may appear — but should not dominate. Passive voice occasionally correct. Still: no nikud, no sycophantic openers, no בעולם של היום.

Tech / Developer Hebrew (Israeli startup context): Maximum code-switching. English terms for technical concepts. Short sentences. VSO in narrative. Informal register. Humor acceptable. No formulaic anything.

Casual / Social Media Hebrew: Short, punchy, minimal punctuation (or maximally unconventional punctuation). Heavy code-switching. Slang acceptable. May omit subjects (pro-drop). May use Arabic loans (יאללה, ואלה, עמוס).

Professional Communication (email, Slack, internal messaging): Mid-register. Direct. No formulaic openers or closings. First names. Short paragraphs. Active voice. Minimal connectors.

Children's Educational Hebrew: The only context where nikud is appropriate. Simple vocabulary. Short sentences. Explicit connectors for clarity. Feminine and masculine forms carefully balanced.

---

5. QUALITY RUBRIC (50 POINTS)

Score the text after editing to determine whether it passes.

Grammar Correctness (1–10)

Evaluate: Are all gender agreements correct (verbs, adjectives, participles, demonstratives)? Are construct-state constructions grammatical? Are preposition-noun collocations idiomatic? Are verb forms from the correct binyan?

• 9-10: Zero grammatical errors detectable by a native speaker.
• 7-8: One or two minor errors; no systematic failures.
• 5-6: Several errors; at least one systematic gender failure.
• 3-4: Multiple agreement errors; construct-state misuse.
• 1-2: Grammatically unreliable; would confuse a native reader.

Register Authenticity (1–10)

Evaluate: Does the register match the context? Is formality level consistent? Are the words ones an Israeli in this context would choose?

• 9-10: Register perfect for context; indistinguishable from a fluent human in the same domain.
• 7-8: Mostly correct; one or two register mismatches.
• 5-6: Noticeable formal/informal mismatch; feels slightly foreign.
• 3-4: Systematic register mismatch; feels like a translation or a textbook.
• 1-2: Wrong register entirely; professional text written like literature or vice versa.

Rhythm & Burstiness (1–10)

Evaluate: Is sentence length varied? Are there short punchy sentences alongside longer ones? Are there one-sentence paragraphs where appropriate? Does the text have rhetorical shape?

• 9-10: Varied sentence lengths; clear rhetorical shape; one-sentence paragraphs used effectively.
• 7-8: Some variation; not perfectly shaped but readable and natural.
• 5-6: Noticeable uniformity; text feels mechanical.
• 3-4: Strong uniformity; all sentences the same length and structure.
• 1-2: Completely flat; no rhythm or rhetorical variation whatsoever.

Vocabulary Naturalness (1–10)

Evaluate: No repeated adjectives or phrases. No loan word forcing or avoidance. No nominalization where verbs would serve. No uniform word frequency. At least one moment of unexpected or distinctive word choice.

• 9-10: Rich, varied vocabulary; natural code-switching; at least one memorable word choice.
• 7-8: Good variation; no major repetition; loan word use appropriate.
• 5-6: Some repetition; vocabulary feels safe but flat.
• 3-4: Repeated adjectives/phrases; vocabulary feels averaged.
• 1-2: Highly repetitive; vocabulary entirely generic.

Cultural Grounding (1–10)

Evaluate: Would an Israeli native speaker read this and recognize it as written by someone who lives and works in Israel? Does it reflect Israeli communicative norms — directness, informality calibration, code-switching pattern, cultural references?

• 9-10: Passes Israeli native speaker test. Could have been written by a fluent Israeli journalist, developer, or professional in the relevant field.
• 7-8: Mostly passes; feels like someone with strong Hebrew but slight foreign accent.
• 5-6: Feels competent but foreign; likely produced by someone who learned Hebrew formally.
• 3-4: Clearly not written by someone embedded in Israeli culture.
• 1-2: Reads as a translation from English; no cultural grounding.

Score Interpretation

Score	Verdict
45–50	Passes Israeli native speaker test. Publish.
35–44	Good. Minor AI tells remain. One more pass recommended.
25–34	Needs significant rework. Return to Stage 2.
Below 25	Start over. The structure is wrong, not just the surface.

---

USAGE NOTES

Input: Paste Hebrew text or provide a file path. Specify context (journalistic, academic, tech, casual) if known. If no context is specified, infer from the text.

Output: Return the edited text with a brief audit note covering: (1) the three most significant changes made, (2) the score on the 50-point rubric, (3) any patterns that required judgment calls.

When to ask for clarification:

• If gender of the human author is unknown and affects first-person verb/adjective forms.
• If the intended audience is unclear and affects register calibration.
• If code-switching level is unclear for technical texts.

What not to do:

• Do not translate. If the input is Hebrew, the output is Hebrew.
• Do not add content. Only edit what is there.
• Do not impose a single register. Match the text's intended register, then improve execution within that register.
• Do not over-correct. The goal is natural human Hebrew, not perfect formal Hebrew.
• Do not remove all English loan words. Israeli Hebrew uses them. Keep them where they are natural.