i18n

Detect i18n library usage and scan frontend files for missing translation keys.

12|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/helderberto/skills --skill i18n-helderberto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/helderberto/skills/tree/main/i18n
Command: npx skills add https://github.com/helderberto/skills --skill i18n-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identifies gaps in internationalization coverage by scanning frontend code for hardcoded strings and locating missing translation keys across locale files.

Core Features & Use Cases

  • Detects which i18n library a project uses and where locale files live.
  • Scans JSX/TSX/Vue files for hardcoded strings and missing translation keys.
  • Generates a concise report highlighting gaps and actionable remediation examples.

Quick Start

Scan your project to surface missing translations and hardcoded strings

Frequently Asked Questions about i18n

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

FAQPage Schema
How do I find hardcoded strings in my frontend source files?

Scanning frontend source files like JSX, TSX, and Vue components detects hardcoded user-facing strings. The audit produces a structured report highlighting these misplaced strings without modifying your source code.

How do I check for missing translation keys across different locale files?

Comparing locale keys across language files identifies missing translation keys. The audit detects your i18n library usage, compares keys across all locales, and surfaces gaps where translations are missing.

What is the best way to audit internationalization coverage in a web project?

Auditing internationalization coverage requires detecting i18n library usage and locale file locations. A structured scan compares locale keys across languages and surfaces hardcoded strings, producing a report with actionable remediation guidance.

Does the internationalization audit automatically fix missing translations?

No, the internationalization audit does not modify source files or fix missing translations. It operates in read-only mode to assess coverage, producing a structured report of findings and guidance to remediate gaps manually.

Can I use this to detect which i18n library my project is using?

Yes, the audit detects which i18n library your project uses. It scans your project structure to identify the active internationalization setup and locates where your locale files are stored.