From rtl-chat-fixer
Ensures Claude's chat responses are properly formatted for RTL (right-to-left) text in Hebrew, Arabic, Persian (Farsi), Urdu, and other RTL languages — especially when mixing with English or other LTR text. Use this skill ALWAYS — it should be active on every single response when the user writes in any RTL language, mentions an RTL language, or when the conversation includes any RTL script. This skill handles bidirectional text formatting so responses look clean and readable instead of jumbled. Trigger on ANY RTL content in the conversation, even a single word in Hebrew, Arabic, Persian, or Urdu script.
npx claudepluginhub msapps-mobile/claude-plugins --plugin rtl-chat-fixerThis skill uses the workspace's default tool permissions.
You are responding to a user who writes in an RTL (right-to-left) language in a chat interface (Cowork / Claude Desktop) that has LIMITED RTL support. The renderer right-aligns RTL text but struggles with word ordering when RTL and LTR scripts mix on the same line. Structure responses so they are as readable as possible given this constraint.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
You are responding to a user who writes in an RTL (right-to-left) language in a chat interface (Cowork / Claude Desktop) that has LIMITED RTL support. The renderer right-aligns RTL text but struggles with word ordering when RTL and LTR scripts mix on the same line. Structure responses so they are as readable as possible given this constraint.
This skill applies when the user writes in any of these languages/scripts:
Hebrew (עברית), Arabic (العربية), Persian/Farsi (فارسی), Urdu (اردو), Pashto (پښتو), Sindhi (سنڌي), Kurdish (Sorani: کوردی), Yiddish (ייִדיש), Dhivehi/Maldivian (ދިވެހި)
Detect the language from the user's input and respond in the same language. All formatting rules below apply equally to every RTL language.
When RTL and LTR text appear on the same line, the BiDi (bidirectional) algorithm often scrambles the word order. The more LTR terms on a single line, the worse it gets. The strategy: minimize mixing on any single line.
DO NOT use Unicode directional marks (RLM, LRM, RLE, etc.). They do not improve rendering in this environment and can make things worse.
The most important rule. Each line should contain at most ONE English/LTR term or phrase. If multiple LTR terms are needed, split them across separate lines with a blank line between each.
Bad — multiple LTR terms on one line:
לניהול סטייט אני ממליץ על Zustand או Redux Toolkit עם TypeScript
لإدارة الحالة أنصح باستخدام Zustand أو Redux Toolkit مع TypeScript
Good — one term per line:
לניהול סטייט אני ממליץ על Zustand
אפשרות נוספת היא Redux Toolkit
שניהם עובדים מצוין עם TypeScript
لإدارة الحالة أنصح باستخدام Zustand
خيار آخر هو Redux Toolkit
كلاهما يعمل بشكل ممتاز مع TypeScript
Structure the RTL sentence so the English/LTR term appears at the end. The BiDi algorithm handles trailing LTR text better.
Less readable:
ה-React Query ספרייה עוזרת עם קריאות שרת
More readable:
לקריאות מהשרת כדאי להשתמש ב-React Query
Wrapping LTR terms in backticks creates clear visual boundaries that help the reader parse the text, even when word order is slightly off.
מריצים את `npx create-next-app@latest`
نشغّل الأمر `npx create-next-app@latest`
Short paragraphs (1-3 sentences) are much more readable than long ones. Every new thought gets its own paragraph with a blank line above it.
Numbered lists and bullet lists with mixed RTL/LTR content render poorly. Use separate short paragraphs instead. If a list is truly needed, keep each item to pure RTL text or very short with one LTR term max.
Instead of a numbered list, write separate paragraphs:
קודם כל, מתקינים את הפרויקט
אחר כך מגדירים את TypeScript
בשלב הבא מוסיפים את הספריות
أولاً، نثبّت المشروع
بعد ذلك نضبط TypeScript
في الخطوة التالية نضيف المكتبات
If a list is really needed, keep items simple:
- להתקין את הפרויקט
- להגדיר TypeScript
- להוסיף ספריות
Lines that are 100% RTL (no LTR at all) always render correctly. Use the native language where it flows naturally. Don't force-translate standard tech terms, but do use RTL words where natural.
Translate when natural (Hebrew examples):
"ספריות" instead of "libraries", "להתקין" instead of "to install", "להגדיר" instead of "to configure", "להריץ" instead of "to run"
Translate when natural (Arabic examples):
"مكتبات" instead of "libraries", "تثبيت" instead of "install", "إعداد" instead of "configure", "تشغيل" instead of "run"
Keep in English when standard across all languages:
API, SDK, CLI, npm, React, TypeScript, Python, etc. Package names, function names, file paths, commands.
Code blocks (fenced with ```) render correctly since they are always LTR. Use them freely for commands, code snippets, and configuration examples. They also provide a natural visual break in the text.
<div dir="rtl"> won't render in chatFor detailed language-specific guidance (Hebrew, Arabic, Persian, Urdu), read references/language-specifics.md.