erp-i18n

Detect hardcoded Vietnamese strings and generate locale files for the CIC ERP application.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/anhnq-lab/cic-erp-contract --skill erp-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erp-i18n
Source: https://github.com/anhnq-lab/cic-erp-contract/tree/main/.agent/skills/erp-i18n
Command: npx skills add https://github.com/anhnq-lab/cic-erp-contract --skill erp-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of making the CIC ERP application accessible to a global audience by managing its internationalization (i18n) and localization efforts. It streamlines the process of identifying and replacing hardcoded text with translatable keys, ensuring a consistent and maintainable multilingual experience.

Core Features & Use Cases

  • Hardcoded String Detection: Identifies hardcoded Vietnamese strings within the codebase using defined patterns and regular expressions.
  • Translation Key Generation: Establishes a structured approach for creating translation keys (e.g., module.section.key).
  • Locale File Creation: Generates and maintains locale files (e.g., vi.json, en.json) in a specified format.
  • Translation Hook Implementation: Provides a useTranslation hook for easy integration of translated strings into the application.
  • Use Case: When preparing the CIC ERP for international release, this skill can systematically scan the entire codebase, identify all user-facing Vietnamese text, and generate the necessary translation files and code to support English and other languages.

Quick Start

Scan the codebase for hardcoded Vietnamese strings and prepare locale files for internationalization.

Frequently Asked Questions about erp-i18n

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

FAQPage Schema
How do I detect hardcoded Vietnamese strings in my ERP codebase for internationalization?

Internationalization of hardcoded Vietnamese strings in an ERP codebase uses defined patterns and regular expressions to detect static text. This process identifies user-facing Vietnamese text so it can be replaced with dynamic translation keys for multilingual support.

What is the best way to structure translation keys for ERP application localization?

Structuring translation keys for ERP application localization follows a hierarchical format like module.section.key. This organization ensures translation files remain maintainable and systematically categorize locale strings by application modules and sections.

How do I generate locale files for an ERP application transitioning to multilingual support?

Generating locale files for ERP multilingual support involves creating JSON files like vi.json and en.json. These files store the translated strings mapped to their respective translation keys, enabling dynamic language switching.

Does this i18n skill implement a translation hook for integrating dynamic text into ERP modules?

Yes, the i18n skill implements a custom useTranslation hook to integrate dynamic translated text into ERP modules. This hook replaces static Vietnamese text by fetching the corresponding values from the generated locale files.

Can I prioritize specific modules like navigation and forms when localizing an ERP application?

Yes, you can prioritize localizing specific ERP modules like navigation, common actions, and forms. The skill targets these high-traffic areas first to efficiently establish a multilingual experience before processing less critical sections.

Why replace static text with translation keys during ERP internationalization?

Replacing static text with translation keys during ERP internationalization ensures a consistent and maintainable multilingual experience. It decouples hardcoded Vietnamese strings from the UI, allowing locale files to manage multiple languages dynamically.