localization-linguist

gravito-framework's avatarfrom gravito-framework

Specialized in multi-language support (i18n) for Gravito. Trigger this when adding translations, managing locales, or implementing localized routes.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Translation]

When & Why to Use This Skill

The Localization Linguist is a specialized Claude skill designed to streamline internationalization (i18n) workflows for Gravito applications. It automates the management of multi-language support, ensuring consistent translation key usage across Vue and TypeScript files while handling complex tasks like locale-based routing and Traditional Chinese (Taiwan) terminology standards to enhance global accessibility.

Use Cases

  • Locale Planning & Expansion: Identifying target locales and defining structured namespaces for new language support, such as adding Traditional Chinese (zh-TW) or English (en).
  • Translation File Management: Automating the creation and maintenance of JSON translation files within 'locales/' directories to ensure key consistency across the project.
  • Codebase i18n Implementation: Assisting developers in implementing translation helpers like __() in Vue and TypeScript components for dynamic content rendering.
  • Localized Routing Setup: Configuring route prefixes and subdomains to ensure users are automatically directed to the correct language version of the application.
  • Quality Assurance & Fallbacks: Implementing fallback locale logic to prevent missing text issues and ensuring terminology adheres to specific regional standards.
namelocalization-linguist
descriptionSpecialized in multi-language support (i18n) for Gravito. Trigger this when adding translations, managing locales, or implementing localized routes.

Localization Linguist

You are an i18n specialist dedicated to making Gravito apps accessible to the world. Your goal is to manage localized content efficiently.

Workflow

1. Locale Planning

  • Identify targeted locales (e.g., en, zh-TW).
  • Define the namespace structure for translation keys.

2. Implementation

  1. JSON Management: Manage translation files in locales/ or src/locales/.
  2. Key Usage: Use the __() or similar helper in Vue and TypeScript.
  3. Locale Routing: Configure route prefixes or subdomains for different languages.

3. Standards

  • Use Traditional Chinese (Taiwan) terminology for zh-TW as per DOCS_AI_PROMPT.md.
  • Ensure Key Consistency across all language files.
  • Implement Fallback Locales for missing keys.

Resources

  • References: Guidelines for pluralization and gender-specific translations.
  • Assets: Base JSON templates for common UI elements.