Generate right-to-left CSS variants from LTR stylesheets before multilingual launches with RTLCSS
Use RTLCSS when an agent already has left-to-right stylesheets and must prepare a right-to-left variant for Arabic, Hebrew, or other RTL interfaces. The skill transforms directional CSS rules into an RTL companion stylesheet so localization work does not require hand-editing every margin, padding, float, and alignment rule.
npx skills add agentskillexchange/skills --skill generate-right-to-left-css-variants-from-ltr-stylesheets-before-multilingual-launches-rtlcss
Tool: RTLCSS is an open source framework and npm package for converting left-to-right CSS into right-to-left CSS. In ASE, the useful skill-shaped framing is narrow: an agent takes an existing stylesheet that was authored for LTR layouts, generates an RTL counterpart, and returns it for a multilingual build, preview, or deployment step.
What this skill actually does
What the agent does: it runs RTLCSS against prepared CSS assets, flips directional declarations where appropriate, preserves non-directional rules, and emits an RTL-ready stylesheet for downstream packaging. That is valuable during website localization, white-label theming, email template localization, design-system exports, and release preparation for products that need Arabic or Hebrew support without manually rewriting every selector.
When to use it: invoke this when the task is specifically “produce the RTL stylesheet from the existing LTR source.” Do not invoke it as a generic CSS framework listing or as a stand-in for translation work. The agent uses it after UI strings and layout requirements already exist and before the localized build is shipped.
Scope boundary: this skill does not translate copy, audit locale coverage, redesign components, or test the final UX. It strictly handles directional stylesheet transformation.
Integration points: frontend build scripts, localization pipelines, CMS theme exports, email template variants, and CI steps that generate release assets per locale. Upstream evidence is strong: official GitHub repo, npm package, MIT license, public documentation, tagged releases, and ongoing adoption.