i18n-translation

Detect hardcoded strings and enforce ngx-translate key conventions in UI components.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill i18n-translation-reeinharddd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-translation
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/i18n-translation
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill i18n-translation-reeinharddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures all user-facing text in the application is properly internationalized, preventing hardcoded strings and enabling seamless translation into multiple languages.

Core Features & Use Cases

  • Hardcoded String Detection: Identifies and flags any user-facing text that is not managed by the translation system.
  • Translation Key Generation: Helps in creating standardized translation keys following a defined convention.
  • Use Case: When a new button or label is added to a UI component, this Skill can be invoked to ensure the text is wrapped in a translation pipe and a corresponding key is added to the locale files.

Quick Start

Use the i18n-translation skill to check the component file 'path/to/component.ts' for hardcoded strings and add necessary translation keys.

Frequently Asked Questions about i18n-translation

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

FAQPage Schema
How do I detect hardcoded strings in Angular UI components?

To detect hardcoded strings in UI components, the Skill scans your component files and flags any user-facing text that is not managed by the translation system. It then ensures those strings are wrapped in a translation pipe.

What is the naming convention for ngx-translate keys?

The naming convention for ngx-translate keys follows the MODULE.SECTION.KEY_NAME structure. This Skill enforces this standardized format to maintain consistency across your locale files and application modules.

How do I add internationalization to dynamic values and pluralization?

To internationalize dynamic values and pluralization, the Skill validates and supports these features within your translation definitions. It ensures dynamic variables and plural forms are correctly handled by the translation system.

Can I use this to check component files for missing translation keys?

Yes, you can check component files for missing translation keys by invoking this Skill on a specified file path. It identifies unmanaged text, wraps it with a translation pipe, and adds the corresponding key to your locale files.

Does this Skill validate locale file consistency for frontend internationalization?

Yes, this Skill validates locale file consistency for frontend internationalization. It checks that all generated translation keys exist across your locale files to prevent missing translations during UI rendering.