Add skill: mapbox-internationalization-patterns

Summary

Mapbox has specific support for internationalized maps - RTL text, non-Latin scripts, locale-aware label ordering - but AI assistants don't know the correct configuration. Developers building maps for global audiences frequently get this wrong.

Topics to cover

• RTL text - mapbox-gl-rtl-text plugin setup, when it's required, common initialization errors
• Non-Latin scripts - CJK, Arabic, Hebrew, Devanagari label rendering and font requirements
• Language switching - using setLayoutProperty to swap label language dynamically
• Locale-aware label ordering - text-field expressions for multilingual labels
• Font stacks - Mapbox font glyphs for non-Latin scripts, fallback fonts
• Right-to-left UI - integrating an RTL map in an RTL web/mobile layout

Key patterns a skill should teach

• Correct RTL plugin initialization order (must load before map)
• The ['coalesce', ['get', 'name_en'], ['get', 'name']] pattern for language fallback
• How to set the map's display language to match the user's locale
• Common mistakes: forgetting the RTL plugin, using name fields that don't exist in all regions

Why this matters

Maps for global products are common. Without guidance, AI assistants skip RTL plugin setup entirely or use name fields that don't exist for all regions.

No target file, test, or entry point is named; first locate how existing skills are structured in the repository and identify the corresponding skill content location. Done means documenting the listed RTL, script, language-switching, label-ordering, font, and locale integration patterns, including the stated fallback and common mistakes.