i18n-localization

Detect hardcoded strings and validate locale key coverage across codebases.

8.1k|1.5k|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/vudovn/antigravity-kit --skill i18n-localization-vudovn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/vudovn/antigravity-kit/tree/main/.agent/skills/i18n-localization
Command: npx skills add https://github.com/vudovn/antigravity-kit --skill i18n-localization-vudovn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Internationalization and localization are error-prone when strings are hardcoded and locale files drift apart. This Skill helps detect hardcoded strings, audit locale coverage, and guide localization readiness across projects.

Core Features & Use Cases

  • Detect hardcoded UI strings in React, Vue, and Python projects.
  • Validate locale files for consistent keys across languages.
  • Generate actionable reports to improve translations and RTL support.

Quick Start

To begin, run the i18n checker against your codebase: python scripts/i18n_checker.py /path/to/your/project

Frequently Asked Questions about i18n-localization

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

FAQPage Schema
How do I detect hardcoded strings in React and Vue projects for i18n?

To detect hardcoded strings for i18n, this skill scans React and Vue codebases to identify unlocalized UI text and enforces standard usage patterns like t(), $t, and FormattedMessage components.

How do I validate locale files for missing or extra translation keys?

You validate locale files by running the i18n checker script against your project, which examines locale schemas to ensure keys match across languages and flags any missing or extra keys.

Does this i18n localization tool work with Python gettext workflows?

Yes, this i18n localization tool works with Python projects by validating gettext usage patterns and auditing locale coverage to ensure services are ready for translations.

What is the best way to audit codebase readiness for localization?

The best way to audit localization readiness is to run a codebase scan that detects hardcoded strings, enforces i18n patterns, and generates actionable reports on translation gaps.

Can I standardize i18n patterns across both web apps and Python services?

Yes, you can standardize i18n patterns across web apps and Python services by examining locale files and enforcing consistent translation function usage across React, Vue, and Python projects.