RTL Layout Checker

What it does

Scans theme templates and stylesheets for hardcoded left and right values, margins, padding, float, text-align, and positioning, that won't flip correctly under RTL, and lists each occurrence with the file and line so a developer can fix or convert it to a logical property. Also checks common trouble spots like icon direction, navigation menus, and form field alignment that are easy to miss in an LTR-only review.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/rtl-layout-checker/ (or ~/.claude/skills/rtl-layout-checker/ for all projects)

GitHub Copilot (VS Code)

.github/skills/rtl-layout-checker/

OpenAI Codex

.codex/skills/rtl-layout-checker/

Cursor

.cursor/skills/rtl-layout-checker/ (or ~/.cursor/skills/rtl-layout-checker/ globally)

Compatibility

Any WordPress site preparing an RTL locale, such as Arabic or Hebrew, via a multilingual plugin; requires read access to the active theme's template and CSS files.

The complete SKILL.md for this skill:

---
name: rtl-layout-checker
description: Use when a user wants a theme checked for right-to-left layout issues before an RTL locale launches, or asks to "check RTL support" or "audit for Arabic layout".
---

# RTL Layout Checker

## When to use
An RTL locale, like Arabic or Hebrew, is about to launch and the user wants the active theme checked for layout issues before real visitors see it broken.

## Procedure
1. Scan the active theme's CSS for hardcoded left and right properties, margin-left, float: left, text-align: left, left or right positioning, instead of logical properties.
2. List each occurrence with file name and line so a developer can review and convert it.
3. Check navigation menus, breadcrumbs, and icons such as arrows and chevrons for direction that would look wrong flipped, since these often need an explicit RTL override rather than automatic mirroring.
4. Check form fields and any custom layout components for alignment that assumes left-to-right reading order.
5. Summarize findings as a prioritized punch list, highest-visibility issues, header and main navigation, first.

## Guardrails
- This produces a list of issues and locations only, it doesn't rewrite theme CSS automatically since layout changes need visual verification.
- Don't assume WordPress's built-in RTL stylesheet handling covers everything, custom theme CSS still needs this manual check.