rtl-chat

Format chat responses to prevent RTL/LTR word-order errors.

8|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill rtl-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rtl-chat
Source: https://github.com/MSApps-Mobile/claude-plugins/tree/main/plugins/rtl-chat-fixer/skills/rtl-chat
Command: npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill rtl-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Chat renderers with limited RTL support often scramble word order when right-to-left scripts mix with left-to-right text, making responses hard to read and confusing for speakers of Hebrew, Arabic, Persian, Urdu, and other RTL languages. This Skill provides a clear set of formatting rules and response patterns to produce readable, predictable chat output in those languages.

Core Features & Use Cases

  • Detects RTL input and matches the user's language for the response to preserve natural reading flow.
  • Minimizes mixed-direction errors by enforcing one LTR term per line, placing LTR terms at the end of lines, and keeping paragraphs short.
  • Preserves readability for technical content by recommending inline code-style formatting for commands and code blocks for longer examples, while avoiding Unicode directional controls and HTML dir attributes.
  • Use Case: Replying to a bilingual developer asking how to install a package in Hebrew or Arabic without producing jumbled lines when English package names or commands appear.

Quick Start

When the user writes in Hebrew, Arabic, Persian, or Urdu, format each response to minimize RTL/LTR mixing by keeping paragraphs short, placing any English term at the end of its line, and separating multiple English terms onto their own lines.

Frequently Asked Questions about rtl-chat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does mixed RTL and LTR text scramble word order in chat interfaces?

Mixed RTL and LTR text scrambles word order because chat renderers with limited bidirectional support fail to properly resolve character directionality. This causes Hebrew, Arabic, Persian, or Urdu text to render unpredictably when English terms are inserted.

How do I format bilingual chat responses to prevent bidirectional rendering errors?

To prevent bidirectional rendering errors, format responses by minimizing LTR mixing per line, placing English terms at line ends, keeping paragraphs short, and using inline code-style marking for technical terms.

Does this approach use Unicode directional controls to fix Hebrew and Arabic text?

No, this approach avoids Unicode directional controls and HTML dir attributes. It instead enforces structural formatting rules like one LTR term per line and inline code-style formatting to ensure predictable RTL rendering.

Can I use this for technical messages containing code blocks and commands?

Yes, you can use this for technical messages. It preserves fenced code blocks for longer commands and recommends inline code-style formatting for technical terms to maintain readability in RTL conversations.

What is the best way to handle multiple English package names in an Arabic chat response?

The best way to handle multiple English package names is separating each term onto its own line and positioning them at line ends. This minimizes mixed-direction errors in Arabic chat responses.

When do I need bidirectional text formatting for chat applications?

You need bidirectional text formatting when users send mixed RTL and LTR messages in languages like Hebrew, Arabic, Persian, or Urdu. It ensures responses remain readable when English commands or package names appear alongside RTL scripts.