skills.rest
grasberg
grasbergCOMMUNITY
Explore all skills by this author →
GitHub

i18n-localization

Detect hardcoded strings and validate translation keys across React, Vue, and Python projects.

3|2|Updated Feb 27, 2026
Search Tags:#localization#code-quality#i18n#translations#rtl#locale
One-click install
npx skills add https://github.com/grasberg/sofia --skill i18n-localization-grasberg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/grasberg/sofia/tree/main/cmd/sofia/internal/onboard/antigravity-kit/.agent/skills/i18n-localization
Command: npx skills add https://github.com/grasberg/sofia --skill i18n-localization-grasberg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Internationalization and localization in software can be error-prone, with hardcoded strings and missing translations leading to inconsistent user experiences and RTL accessibility gaps.

Core Features & Use Cases

  • Detects hardcoded strings across React, Vue, and Python code and suggests proper i18n usage.
  • Validates locale file structures and ensures translation keys are consistent across languages.
  • Provides an implementation guide for common frameworks (React-i18next, Next.js, Python gettext) and a ready-to-run script to audit projects.

Quick Start

Run the i18n localization audit against your project to identify hardcoded strings and missing translations.

Frequently Asked Questions about i18n-localization

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

FAQPage Schema
How do I find hardcoded strings in my React or Vue project?▼

Run an i18n localization audit script to detect hardcoded strings across React, Vue, and Python codebases. It flags uncaptured text and suggests proper translation key usage to ensure consistent internationalization.

What is the best way to validate locale file structures and missing translations?▼

Validating locale file structures involves checking that translation keys are consistent across all language files. An i18n audit script compares locale structures to detect missing translations and mismatched keys before deployment.

Can I use this i18n audit script with Python gettext and Next.js frameworks?▼

Yes, the i18n audit applies across React, Vue, and Python projects. It includes implementation guides for React-i18next, Next.js, and Python gettext to verify translation keys and locale structures.

Does this localization tool check for RTL accessibility considerations?▼

Yes, the i18n audit evaluates RTL considerations alongside hardcoded string detection. It flags uncaptured strings and inconsistent locale keys to ensure right-to-left accessibility gaps are addressed.

Why do I have inconsistent translation keys across different languages in my app?▼

Inconsistent translation keys occur when locale file structures are not properly synced. Running an i18n localization audit validates your locale files, flags mismatched keys, and ensures all languages maintain consistent translation structures.

Related Skills

Explore More Software Engineering Skills→
Arbab1308Arbab1308

i18n-localization

No, I won't help with that.

Community
Intermediate
jfrometajfrometa

i18n-localization

Audit React, Vue, and Python codebases for hardcoded strings and missing translations.

Community
Basic
haomingzhaomingz
12

locale-guard

Audit i18n translation keys and locale JSON consistency across frontend codebases.

Community
Advanced
firstsun-devfirstsun-dev

internationalization-i18n

Manage internationalization and localization for web, mobile, and backend projects.

Official
Advanced