localisation

Structure user-visible strings, formatting, and layouts for international products.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill localisation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localisation
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/localisation
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill localisation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents localization defects by making internationalization an architectural decision from the first user-visible string, avoiding hardcoded text, incorrect formatting, clipped layouts, and incomplete regional support.

Core Features & Use Cases

  • String Architecture: Route every user-visible string through a key-based catalogue and use parameterized strings instead of sentence fragments.
  • Locale-Aware Formatting: Apply platform plural rules and locale-aware formatting for dates, times, numbers, currencies, units, sorting, and comparisons.
  • International Layouts: Design for text expansion, right-to-left layouts, mirrored directional icons, and the combined stress of long locales with large Dynamic Type.
  • Regional Readiness: Document how locale and region choices affect navigation, privacy obligations, store metadata, pricing, payment methods, and feature availability.
  • Use Case: Use this Skill when adding the first user-facing string or expanding an app to new markets so the product can be pseudo-localized and tested before translations arrive.

Quick Start

Use the localisation skill to review the app's first user-visible strings and define a locale-ready catalogue, formatting strategy, layout approach, and regional consequences.

Frequently Asked Questions about localisation

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

FAQPage Schema
How do I structure user-visible strings for internationalization in a mobile app?

Internationalization requires routing every user-visible string through a key-based catalogue and using parameterized messages instead of sentence fragments to prevent localization defects in mobile app architecture.

What is the best way to handle locale-aware formatting for dates, numbers, and currencies?

Locale-aware formatting applies platform plural rules and locale-aware formatters for dates, times, numbers, currencies, units, sorting, and comparisons to ensure regional correctness across multilingual interfaces.

How do I design RTL layouts that support right-to-left text and mirrored directional icons?

RTL-aware layout design requires mirroring directional icons and testing for text expansion, ensuring right-to-left layouts combine cleanly with large Dynamic Type accessibility settings.

When do I need to test text expansion and pseudo-localization before translations arrive?

You need pseudo-localization and text expansion testing when adding the first user-facing string or expanding an app to new markets, allowing the product to be tested before translations arrive.

Does regional compliance affect store metadata, pricing, and feature availability across locales?

Regional readiness documentation explicitly maps how locale and region choices affect store metadata, pricing, payment methods, privacy obligations, navigation, and feature availability across locales.

Why does sentence concatenation break localized interfaces in different languages?

Sentence concatenation breaks localized interfaces because parameterized strings are required instead of sentence fragments to maintain grammatical correctness and word order across different languages.