internationalization

Define locale surfaces, fallback rules, and formatting guidelines for QA checks.

1|Updated Mar 17, 2026

Search Tags:#formatting #localization #translation #i18n #l10n #locale

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill internationalization-yknothing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: internationalization
Source: https://github.com/yknothing/prodcraft/tree/main/skills/cross-cutting/internationalization
Command: npx skills add https://github.com/yknothing/prodcraft --skill internationalization-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures and enforces locale-specific behavior for user-facing text, date/number formatting, and language fallbacks to ensure consistent experiences across locales.

Core Features & Use Cases

Define locale surface: identify strings, formats, and locale decisions touched by changes.
Capture fallback rules and formatting requirements to handle missing translations and locale gaps.
Apply reviews to verify locale behavior across surfaces and QA checks.

Quick Start

Define the locale surface, specify fallback behavior, and formalize formatting rules for a new feature.

Frequently Asked Questions about internationalization

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

FAQPage Schema

How do I define a locale surface for new UI text and formatting?▼

To define a locale surface, identify all user-facing strings, date and number formats, and specific locale decisions impacted by new feature changes. This process captures the translation scope and formatting guidelines required for consistent localization behavior across product interfaces.

What is the best way to handle language fallbacks for missing translations?▼

Handling language fallbacks requires capturing explicit fallback rules within your localization strategy. This ensures that when specific translations are missing, the system defaults to a designated locale, maintaining a consistent user experience across all supported languages.

How do I standardize locale-specific date and number formatting across an application?▼

Standardizing locale-specific formatting involves formalizing formatting guidelines that apply across all product interfaces. Defining these rules ensures consistent presentation of dates, numbers, and text according to each specific locale's requirements.

Can I use locale rules to automate QA checks for user-facing text?▼

Yes, defining the locale surface and formatting requirements enables consistent QA checks. By formalizing translation scope and fallback rules, you can apply automated reviews to verify correct locale behavior across all user-facing surfaces.

When do I need to specify translation scope and fallback behavior?▼

You need to specify translation scope and fallback behavior when adding new features that touch user-facing text. Capturing these locale rules early prevents formatting inconsistencies and ensures proper handling of missing translations across different languages.