cursor-rtl-visual-fix

name	cursor-rtl-visual-fix
description	Fix Cursor RTL rendering issues end-to-end with visual verification. Use when the user provides a cursor-ext-rtl GitHub issue, mentions RTL visual bugs, Markdown tables, Hebrew/Arabic/Persian layout, Cursor chat rendering, or asks to develop and visually test a fix.

Cursor RTL Visual Fix

Use this skill to take an RTL rendering issue from report to verified fix in this repository.

Operating Rules

• Treat the issue screenshot/description as the product requirement.
• Do not commit or push unless the user explicitly asks.
• Use npm run package to create a VSIX. Do not run vsce package directly.
• Preserve unrelated user changes. Do not revert files you did not need to touch.
• Visual evidence is required for UI/layout fixes. DOM checks are supporting evidence only.
• Never approve or update visual baselines without explicit user confirmation after they review visual/actual.

End-to-End Workflow

1. Understand the issue.

   • If given a GitHub issue URL, use gh issue view <number> --repo motcke/cursor-ext-rtl --comments when possible.
   • Extract the failing scenario, expected layout, actual layout, affected UI surface, and any screenshot clues.
   • For example, issue #8 is about mixed Hebrew and English text being misaligned in Markdown tables.

2. Inspect the current implementation.

   • Start with resources/rtl.js; most visual behavior is injected from there.
   • Check related selectors, direction rules, unicode-bidi, text-align, table handling, code block exclusions, and scanner behavior.
   • Search before editing. Prefer the repo's existing CSS/DOM-injection patterns.