mcpField
A
arabic-rtl-fixer-ai-skill

arabic-rtl-fixer-ai-skill

github.com/ibadwiDocuments4868 installsUpdated 8w ago
Repository

About arabic-rtl-fixer-ai-skill

arabic-rtl-fixer-ai-skill provides Arabic, Unicode, right-to-left, and compatibility guidance for skills creating or repairing documents and other formats. It emphasizes preserving content and using native direction and layout features, with separate audit and repair workflows for bundled OOXML tools.

Key features

  1. 01Logical-order Arabic Unicode handling
  2. 02Native RTL direction and alignment guidance
  3. 03Format-specific authoring references
  4. 04Rendered and target-application QA steps
  5. 05Separate read-only audit and repair commands
  6. 06Repair output preserves the source file

Use cases

  1. 01Preparing Arabic-first or bilingual documents
  2. 02Checking RTL text and mixed-direction content
  3. 03Auditing or repairing OOXML files
  4. 04Verifying Arabic layout in a target application

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ibadwi/arabic-rtl-fixer-ai-skill --skill arabic-rtl-fixer-ai-skill

After installing, type/arabic-rtl-fixer-ai-skillin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

CONTRIBUTING.md
SECURITY.md
LICENSE
README.md
THIRD_PARTY_LICENSE.md
.github/ISSUE_TEMPLATE/
feature_request.yml
bug_report.yml
.github/workflows/
test.yml
agents/
openai.yaml
examples/
README.md
references/
documents-and-pdf.md
digital-formats.md
qa.md
presentations.md
unicode-and-writing.md
scripts/
generate_examples.py
arabic_docx.py
arabic_pptx.py
tests/
test_arabic_docx.py
test_arabic_pptx.py

Details

From the project README

Arabic Content Quality

Use this skill as the Arabic language, Unicode, RTL, and compatibility layer on top of the skill for the requested output format. Preserve the user's content, design, and target format.

Core contract

  • Store Arabic in normal logical Unicode order. Never reverse characters, words, or lines and never pre-shape letters into Arabic Presentation Forms.
  • Do not add invisible bidi controls (RLE, LRE, RLO, LRO, PDF, RLI, LRI, FSI, PDI, LRM, RLM, or ALM) as a general RTL fix. Use native paragraph, container, or document direction.
  • Do not delete ZWJ or ZWNJ blindly; they may be linguistically meaningful. Flag unexpected occurrences and remove them only when safe.
  • Set Arabic language metadata (ar-SA unless the requested locale differs), native RTL direction, and intentional alignment independently.
  • Keep long English passages, URLs, email addresses, file paths, citations, formulas, and code in separate LTR containers when the format permits.
  • Choose a font with Arabic glyph coverage. Do not claim a font is embedded or portable unless verified. Supply PDF when fixed appearance matters.
  • Use native list and numbering features. Do not fake bullets, indentation, tables, or reading order with spaces or typed glyphs.
  • Preserve editable source files whenever editability is requested; PDF is a fixed-output companion, not a replacement.

Read references/unicode-and-writing.md whenever authoring or repairing Arabic text. Then read only the reference for the target format:

Workflow

  1. Identify the Arabic locale, target application, editable source format, and whether the artifact is Arabic-first or bilingual. Infer these from the request when safe.
  2. Author plain Unicode text, applying RTL through native format properties rather than invisible characters.
  3. Separate incompatible base directions at paragraph, text-box, cell, or component boundaries.
  4. Validate structure, then render the whole artifact and inspect Arabic shaping, ordering, wrapping, punctuation, numbers, bullets, tables, overflow, and font substitution.
  5. Test in the user's target application when available. Do not treat a secondary renderer as proof of Microsoft PowerPoint, Word, browser, or Google behavior.
  6. Report structural QA, visual/layout QA, target-application QA, and font portability separately. Never claim universal cross-application perfection without testing those applications.

Safe automation boundary

The bundled OOXML tools have separate audit and repair commands. Audit is read-only. Repair must write a distinct output file, preserve the source, and must not overwrite an existing output unless the user explicitly supplies --force. A structural audit does not replace rendered or target-application QA.

Source attribution

The bundled PPTX repair/audit helper is derived from Sultan Alsafran's MIT-licensed arabic-presentations skill. Preserve THIRD_PARTY_LICENSE.md when sharing or modifying this skill.

Comments

Markdown supported