What problem does it solve?
This skill helps you implement Internationalization (i18n) and Localization (l10n) for ObjectStack projects by ensuring translation bundles, locale configuration, and translation key naming remain consistent with your underlying Zod metadata.
Core Features & Use Cases
- Object-first translation bundles: Organize app, navigation, and object/field text so that labels, views, sections, and actions live under the correct
o.{object_name} namespaces.
- Locale configuration and fallback strategy: Set default locale, supported locales, fallback locale, message format (simple vs ICU), and loading behavior to prevent missing-text issues.
- Coverage, missing, redundant, and stale detection: Use coverage reporting to find untranslated keys, orphan keys, and keys that no longer match current metadata.
- AI-assisted translation suggestions workflow: Generate suggestions for missing entries and review them before committing changes.
- Integration guidance with II18nService: Follow the service contract patterns for translating keys, loading bundles, and running coverage/diff workflows.
Quick Start
Use the objectstack-i18n skill to design your translation bundle structure for a new locale and validate coverage against your current object and field metadata.