Hebrew RTL Interface Review
Reviews a Hebrew interface for common RTL failures — directionality, mixed text, numbers, icons, and animation — that look fine to an English-speaking reviewer.
Prompt
Review the following code for RTL failures. Most RTL bugs pass review because they look correct to someone who does not read Hebrew.
Code: <code> [Paste JSX / CSS] </code>
Check:
- Directionality — is dir set on html rather than body. Setting it on body does not override an html-level declaration and creates an inconsistent state.
- Logical properties — margin-inline-start instead of margin-left, padding-inline-end, inset-inline. Every explicit left or right value is suspect until proven otherwise.
- Directional icons — a "next" arrow must flip in RTL; a non-directional icon (checkmark, trash) must not. Go through every icon and decide.
- Mixed text — a Hebrew string containing an English word, URL, file path, or code fragment. Check terminal punctuation — a full stop ending a Hebrew sentence that finishes with a Latin word jumps to the wrong position without bidi isolation.
- Numbers and direction — numbers remain LTR inside RTL text. Check amounts, dates, ranges ("3-5"), and phone numbers.
- Input fields — placeholder, text alignment, caret position, and fields that must stay LTR (email, password, card number).
- Animation and scrolling — transform direction, horizontal scroll, and drawer position. A slide-in from the left reads backwards in Hebrew.
- Overflow — Hebrew text runs 20-30% longer than English on average. Check buttons, tabs, and headings at 390px width.
For each finding: location in the code, what breaks visually, and the fix. Mark severity: breaks usage / looks wrong / polish.
Why this converts well
- Ready to copy and use immediately
- Tailored for legal and public-sector work
- Easy to adapt to internal workflows
Tags
Related Prompts
Tool Specification for a Legal AI Agent
Produces a complete agent tool definition — schema, description, errors, permissions — with emphasis on tools that perform irreversible actions.
Designing a Structured Output Schema for Legal Data
Designs a JSON schema for legal data extraction with explicit representation of uncertainty and missing values instead of silent defaults.
Regression Test Suite for a Production Prompt
Builds a test suite for a prompt before changing it, catching silent regressions introduced by an innocent-looking improvement or a model swap.