i18n

Validate translation coverage across four locales in Nuxt and python-i18n systems.

9|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/bbvch-ai/aihub-core --skill i18n-bbvch-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/bbvch-ai/aihub-core/tree/main/.claude/skills/i18n
Command: npx skills add https://github.com/bbvch-ai/aihub-core --skill i18n-bbvch-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the critical pain point of inconsistent, incomplete, or missing translations across the 4 required Swiss locales (German, English, French, Italian) for the Swiss AI Hub's separate frontend Nuxt and backend python-i18n systems, which leads to broken user experiences, compliance gaps for Swiss enterprise customers, and hours of manual debugging for development teams.

Core Features & Use Cases

  • Full i18n Architecture Reference: Complete documentation of the dual frontend/backend i18n setup, including file structure, naming conventions, LocaleHandler/LocaleString class hierarchies, scope inheritance rules, and guidance on when to create new translation files vs extend existing ones.
  • Deterministic Translation Validation: Includes a built-in script to automatically compare keys across all 4 locales, report missing/extra/empty translations, and calculate coverage percentages for both frontend and backend translation files.
  • Hardcoded String Auditing: Guides developers to scan new code changes for unlocalized user-facing strings in Vue templates and Python code to enforce full translation compliance.
  • Use Case: A developer adding a new RAG agent to the platform can use this Skill to create the correct scoped translation files, run validation to ensure all 4 locales have matching keys, and audit their code for any hardcoded strings that need translation.

Quick Start

Use the i18n skill to run the full translation validation and scan your latest code changes for hardcoded user-facing strings.

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I validate translation coverage across multiple locales in a Nuxt and Python full-stack application?

To validate multi-locale translation coverage across Nuxt and Python-i18n systems, you can run a deterministic script that compares keys across all supported locales, reports missing or empty translations, and calculates coverage percentages.

How do I scan my Vue and Python code for hardcoded user-facing strings?

Scanning Vue templates and Python code for hardcoded user-facing strings is handled through a guided auditing process that detects unlocalized text, ensuring full translation compliance across your full stack.

Does this i18n validation approach support scope inheritance for backend Python translation files?

Yes, the i18n validation approach fully supports scope inheritance for backend Python translation files, maintaining consistent key structures across LocaleHandler and LocaleString class hierarchies for all supported locales.

What is the best way to add new translation keys for a RAG agent across four different locales?

The best way to add new translation keys across four locales is to use a guided workflow that helps create correctly scoped translation files, validates that all locales have matching keys, and audits code for hardcoded strings.

Why do my Nuxt frontend and Python backend translations become inconsistent across supported locales?

Nuxt frontend and Python backend translations become inconsistent due to separate i18n systems lacking synchronized key structures, which requires deterministic translation validation to detect missing, extra, or empty translations across all four supported locales.