Hebrew i18n
Verified90/100Implement comprehensive Hebrew internationalization (i18n) patterns for web and mobile applications. Use when user asks about Hebrew localization, "beinle'umiyut", i18n for Israeli apps, Hebrew plural forms, Hebrew date formatting, RTL CSS logical properties, bidirectional text handling, React/Vue/Angular/Next.js RTL integration, Tailwind CSS RTL, or next-intl setup. Covers Hebrew pluralization rules, date and number formatting for Israel, RTL-first CSS, Tailwind RTL utilities, and bidi text algorithms. Do NOT use for NLP or content writing (use hebrew-nlp-toolkit or hebrew-content-writer instead).
Trust score 90/100 (Verified) · 518+ installs · 2 GitHub contributors · MIT license
Hebrew internationalization goes far beyond text translation. It requires handling RTL direction, Hebrew and Gregorian dates, shekel currency, unique plural forms, and local conventions. Developers unfamiliar with all the nuances discover embarrassing bugs after launch, when the product is already in users' hands.
skills-ilHow to use this skill
Not sure how? Read the guide- 1. Click "Download ZIP" to download the skill files.
- 2. Open Claude Desktop and go to Customize > Skills.
- 3. Click "+" and select "Upload a skill", then upload the ZIP file.
- 4. Start a new conversation. The skill will activate automatically when relevant.
Developers? Install via command line (CLI)
npx skills-il add skills-il/localization@v1.2.2-hebrew-i18n --skill hebrew-i18n -a claude-codeWhen to Apply
- When adding Hebrew language support to an existing app (React, Vue, Angular, Next.js)
- When building a bilingual Hebrew-English application from scratch
- When fixing bidirectional text (bidi) display bugs with phone numbers or URLs in Hebrew UI
- When handling Hebrew plural forms (singular, dual, plural) in translated messages
- When designing CSS that needs to work in both RTL and LTR layouts
Try These Prompts
How do I configure i18n for Hebrew in Next.js with RTL support, including translation file management, page direction, and appropriate fonts?
What is the correct way to format dates, numbers, and currency in Hebrew? Including Israeli shekel and Hebrew calendar dates.
How do I build an app that supports both Hebrew (RTL) and English (LTR) with smooth language switching, including CSS and layout considerations?
How do I use Tailwind CSS with RTL? Which logical utilities should I prefer and what are common pitfalls like space-x not reversing?
Frequently Asked Questions
Changelog
Fix: Intl.DateTimeFormat with he-IL renders the short date dot-separated (DD.MM.YYYY), not slashes; added a note that the many plural category was removed in CLDR 42 (Hebrew uses one/two/other); Tailwind v4 RTL note.
Jun 16, 2026
Removed em-dashes from the guide to comply with the skills-il content style rule.
May 12, 2026
Related Skills
Author: skills-ilGenerate professional Hebrew documents (PDF, DOCX/Word, and PPTX) with correct right-to-left layout, mixed Hebrew-and-English bidi handling, and proper Hebrew typography. Use whenever the output is a Hebrew or mixed Hebrew/English Word document, Hebrew PDF, or Hebrew PowerPoint, including phrasings like "Hebrew Word document", "Word document in Hebrew", "מסמך Word בעברית", "create a .docx in Hebrew", "lehafik heshbonit", and "litstor hozeh", or Israeli templates such as Heshbonit Mas (tax invoice), Hozeh (contract), Hatza'at Mechir (proposal), or Protokol (meeting minutes). ALSO use this for the symptom where a Hebrew document looks correct on screen or in Claude but comes out scrambled, reversed, or broken after export to Word, with English words, numbers, or punctuation landing on the wrong side, phrased as "Hebrew text reversed in Word", "my Hebrew Word file is broken", "fix Hebrew formatting in Word", or "the docx came out messed up"; the fix is regenerating the .docx with paragraph-level RTL/bidi, NOT a web/CSS RTL change. Prefer this over the generic docx or pdf skills ONLY when the document is Hebrew or right-to-left, because those do not set RTL/bidi and produce scrambled Hebrew with English words and punctuation in the wrong place; for English-only documents use the generic skill. Covers reportlab, WeasyPrint, python-docx, and pptxgenjs. Do NOT use for OCR or reading existing documents (use hebrew-ocr-forms instead).
Author: skills-ilWrite and edit professional content in Hebrew including marketing copy, UX text, articles, emails, and social media posts. Use when user asks to write in Hebrew, "ktov b'ivrit", create Hebrew marketing content, edit Hebrew text, write Hebrew UX copy, or optimize Hebrew content for SEO. Covers grammar rules, register from formal to dugri, mixed Hebrew/English, gendered language, nikud and numerals, and Hebrew SEO best practices. Do NOT use for Hebrew NLP/ML tasks (use hebrew-nlp-toolkit) or translation (use a translation skill).
Author: skills-ilImplement right-to-left (RTL) layouts for Hebrew web applications. Use when user asks about RTL layout, Hebrew text direction, bidirectional (bidi) text, Hebrew CSS, "right to left", or needs to build a Hebrew web UI. Covers CSS logical properties, the :dir() pseudo-class, Tailwind RTL, React/Next.js RTL setup, icon mirroring, Hebrew typography, and font selection. Do NOT use for Arabic RTL (similar but different typography) unless user explicitly asks for shared RTL patterns, or for native mobile RTL (React Native I18nManager, SwiftUI, Android) which is out of scope.
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill