objectstack-i18n

Implement ObjectStack i18n translation bundles with locale fallback and coverage checks.

22|6|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/objectstack-ai/framework --skill objectstack-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: objectstack-i18n
Source: https://github.com/objectstack-ai/framework/tree/main/skills/objectstack-i18n
Command: npx skills add https://github.com/objectstack-ai/framework --skill objectstack-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about objectstack-i18n

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

FAQPage Schema
How do I configure i18n locale bundles to match my object and field metadata?

Configure i18n locale bundles by organizing text under object-first namespaces like `o.{object_name}` and `fields.{field_name}` to match your metadata. This ensures labels, views, and actions remain consistent across supported locales.

What is the best way to resolve missing translation warnings during development?

Resolve missing translation warnings by setting a fallback locale and running coverage reporting to identify untranslated keys. AI-assisted translation suggestions can then be generated and reviewed before committing changes.

How do I check translation coverage and find orphan keys in my project?

Check translation coverage and find orphan keys by running coverage and diff checks during development or CI. This detects untranslated, redundant, and stale keys that no longer match current metadata.

Does ObjectStack i18n support ICU message format for locale text?

ObjectStack i18n supports configurable message formats, allowing you to choose between simple text and ICU message format. This configuration applies to loading behavior and prevents missing-text issues across locales.

How do I integrate II18nService operations for loading translations and computing coverage?

Integrate II18nService by following service contract patterns for translating keys, loading bundles, and running coverage workflows. This ensures proper locale-aware bundling and fallback behavior across the application.