- Home
- Skills
- Mobile Development
- App Localization: i18n Setup & Verified Translations
Works with the AI Agents you already use
App Localization: i18n Setup & Verified Translations
End-to-end app internationalization: string extraction, i18n library setup, and context-aware translations.
Free
App Localization: i18n Setup & Verified Translations
Example session with this skill installed
Translate my Next.js App Router project to Spanish and German. Extract all hard-coded strings from the /components folder and set up next-intl.
- Read your context and instructions
- Compiled the app localization
I have audited the /components directory, extracted 14 hard-coded strings, and configured next-intl for Spanish (es) and German (de).
Localization Implementation
I have created the messages directory and updated your navigation to use locale-aware routing. Below is the translation resource file for the Spanish locale.
{
"navigation": {
"home": "Inicio",
"settings": "Ajustes",
"profile": "Perfil"
},
"dashboard": {
"welcome": "¡Bienvenido de nuevo, {name}!",
"lastLogin": "Último inicio de sesión: {date, date, short}",
"notifications": "{count, plural, =0 {No tienes notificaciones} one {Tienes una notificación} other {Tienes # notificaciones}}"
},
"auth": {
"logout": "Cerrar sesión",
"loginError": "Credenciales incorrectas. Por favor, inténtelo de nuevo."
}
}
The following changes were applied
- Created
messages/es.jsonandmessages/de.json. - Configured
i18n.tsandmiddleware.tsfor Next.js App Router. - Refactored
Header.tsxandUserPanel.tsxto useuseTranslations(). - Added
hreflangtags to the root layout for SEO.
Next steps
- Review the
glossary.mdI generated to ensure brand terms like "Agensi" remain untranslated. - Run the build script to verify that
generateMetadatacorrectly handles localized slugs. - Check the
UserPanellayout in German to ensure the longer strings do not cause horizontal overflow.
Connects securely to your tools. The creator never sees your data.
About this skill
Hard-coded strings and manual formatting make scaling to new markets a technical nightmare. This skill automates the end-to-end internationalization (i18n) process, from extracting text to implementing locale-aware routing.
What it does
- Framework detection: Identifies your stack and configures the appropriate i18n library.
- String extraction: Replaces hard-coded UI text with semantic keys and namespaced resource files.
- Context-aware translation: Handles ICU message formats, including complex plurals, gender, and interpolation.
- Regional formatting: Implements native formatters for dates, currencies, and numbers to avoid manual string manipulation.
- RTL support: Applies logical CSS properties and direction attributes for Arabic, Hebrew, and Farsi.
- Validation: Runs pseudo-localization tests to find layout overflows and missing translations.
How it works
- Audit: Scans the codebase to identify existing locales and count hard-coded strings in components, templates, and metadata.
- Configuration: Installs and configures the standard library for your framework (e.g., next-intl for Next.js or ARB files for Flutter).
- Extraction & Glossary: Migrates UI text into JSON or XML resource files while building a brand-specific glossary to ensure consistent terminology.
- Implementation: Updates components to use translation hooks and adds locale-based routing and SEO tags.
Frameworks & tools
Supports React (react-i18next), Next.js (next-intl), Vue (vue-i18n), Angular, Flutter (ARB), iOS (String Catalogs), and Android (strings.xml).
Why this beats prompting it yourself
Generic prompts often fail at complex pluralization rules for languages like Polish or Arabic and ignore logical CSS for RTL layouts. This skill ensures strict adherence to ICU/CLDR standards and prevents string concatenation bugs.
Use cases
- Multi-market expansion: Porting a US-English React app to German and French markets.
- i18n debt reduction: Extracting hundreds of hard-coded strings from a legacy Vue dashboard.
- RTL implementation: Adapting a mobile app layout for Hebrew users.
- Compliance: Ensuring legal and medical terms remain consistent via a locked glossary.
Known limitations
Does not perform human legal review for sensitive terms. Images containing embedded text must be manually converted to text overlays for translation.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Requires manual conversion of text-heavy images. Does not replace human legal/medical review for high-stakes terminology.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 1 day ago
- Free with an Agensi account
Permissions
No special permissions declared or detected