Agent skill · forcedotcom
experience-lwc-rtl-validate
Use this skill to review a Lightning Web Component (.html, .js, .css files) for right-to-left (RTL) internationalization correctness, producing a finding list with code-level fixes covering CSS logical properties, bidirectional text handling, keyboard semantics, and RTL-aware SLDS class usage. TRIGGER when the user says \"review this LWC for RTL\", \"audit i18n compliance\", \"fix bidirectional text rendering\", \"replace left/right CSS with logical properties\", \"check RTL layout issues\", \"verify SLDS RTL classes\", \"review my component for Arabic/Hebrew layout\", \"ensure this LWC works in RTL locales\", or \"check bidi text handling\". DO NOT TRIGGER when the user is building a new LWC (use experience-lwc-generate), refactoring SLDS classes themselves (use design-systems-slds-apply or design-systems-slds2-migrate), or performing accessibility/security review.
What it needs
About 6k tokens when loaded.
What this skill does
<!-- adk-managed-skill --> Reviewing LWC RTL Run a structured right-to-left (RTL) internationalization compliance pass over a Lightning Web Component, producing a report of issues found and code-level fixes to bring the component into compliance with Salesforce RTL guidelines. When to Use The user asks for an "RTL review", "i18n check", "RTL compliance pass", or "RTL audit" on a specific LWC. Preparing a component for release in RTL locales (Arabic, Hebrew, Farsi, Urdu). Investigating layout defects reported in RTL environments. Verifying SLDS class usage after a CSS refactor. Do NOT use this skill for: Building new components (use experience-lwc-generate). Modifying SLDS classes themselves (use design-systems-slds-apply or design-systems-slds2-migrate). Accessibility or security review — run those as separate passes with the relevant tooling. Gating a fix behind a feature flag (apply feature-flag gating after fixes land). Prerequisites Component path (LWC bundle under modules/…). Access to the component's HTML templates, JS/TS, and CSS. Knowledge Base The reference is the source of truth. Do not summarize from memory — open the reference, apply the guidelines, and cite the specific section you used in the report. RTL internationalization: RTL Expert Workflow Step 1 — Scope the review Collect the component path and identify the files to review: .html, .js/.ts, .css, and any child components owned by the same team that are invoked from the target. Note any existing feature-flag gates (e.g., Aura.org.rtlPhase1FixEnabled) — findings that require code changes must respect them. Step 2 — Read the knowledge base Read RTL Expert top-to-bottom before judging. It enumerates the physical-to-logical property mappings, bidirectional text handling patterns, and — critically — the SLDS constraints that override generic RTL advice. Step 3 — CSS inspection Run the deterministic scanner over every .css file in the bundle. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/experience-lwc-rtl-validate