i18n-governance

Standardize RTL-compliant i18n governance for Laravel backend and Nuxt frontend.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill i18n-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-governance
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/i18n-governance
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill i18n-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and enforces RTL-compliant internationalization governance across Laravel backend and Nuxt frontend, ensuring consistent translations, layout direction, and key management.

Core Features & Use Cases

  • Supports Arabic (ar) RTL and English (en) with language-specific translation files for backend (Laravel) and frontend (Nuxt).
  • Enforces translation key rules, locale defaults, and consistent RTL layout across UI components.
  • Provides a clear path for integrating i18n assets into both Laravel and Nuxt projects, with structure examples and best practices.

Quick Start

Create and validate ar/en localization files following the structure outlined, then integrate RTL configurations into layouts and components.

Frequently Asked Questions about i18n-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize RTL internationalization across a Laravel and Nuxt stack?

Standardizing RTL internationalization across Laravel and Nuxt involves applying consistent translation key rules, locale defaults, and layout direction configurations for Arabic and English assets across both backend and frontend projects.

What is the best way to manage translation keys for multilingual apps with Arabic RTL support?

Managing translation keys for RTL Arabic and English requires enforcing strict file structure rules and locale defaults across your stack. This ensures translation keys remain consistent and synchronized between Laravel backend and Nuxt frontend assets.

Can I use this i18n governance approach for projects that only need English and Arabic?

Yes, this i18n governance approach is specifically configured for projects requiring Arabic RTL and English support. It applies language-specific translation files and enforces RTL layout configurations across UI components in both Laravel and Nuxt.

How do I configure locale defaults and layout direction for Nuxt frontend components?

Configuring locale defaults and layout direction for Nuxt components requires integrating RTL configurations directly into your layouts. This ensures consistent layout direction and language-specific rendering across all UI components.

Why does my RTL layout break when switching between Arabic and English locales?

RTL layouts often break due to inconsistent translation key management and missing locale defaults across the stack. Enforcing standardized i18n file structures and RTL layout rules in both Laravel and Nuxt resolves these rendering inconsistencies.