localize

Audits codebases for hardcoded strings and manages translation catalogs across multiple locales.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/iuliandita/skills --skill localize-iuliandita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/iuliandita/skills/tree/main/skills/localize
Command: npx skills add https://github.com/iuliandita/skills --skill localize-iuliandita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the fragmentation and quality gaps in internationalization (i18n) by providing a systematic workflow to audit codebases, extract hardcoded strings, and ensure translation consistency across multiple languages.

Core Features & Use Cases

  • Systematic Audit: Identify hardcoded strings, missing keys, and translation gaps using specialized grep patterns.
  • Quality Assurance: Enforce native orthography, voice consistency, and placeholder integrity through automated validation scripts.
  • Use Case: Use this skill to audit a React application for hardcoded strings, set up a robust i18next infrastructure, and validate that all locale catalogs are complete and free of placeholder errors before deployment.

Quick Start

Use the localize skill to audit the current directory for hardcoded strings and generate a report of missing keys in the locale catalogs.

Frequently Asked Questions about localize

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

FAQPage Schema
How do I audit a codebase for hardcoded strings and missing translation keys?

You can audit a codebase for hardcoded strings and missing translation keys using specialized grep patterns that systematically scan source files and compare them against locale catalogs to identify translation gaps.

Does this i18n extraction approach work with React, Vue, Svelte, and Angular?

Yes, this internationalization extraction approach supports framework-specific patterns for React, Vue, Svelte, and Angular to ensure full coverage of UI text during the translation catalog management process.

What's the best way to validate placeholder syntax across multi-locale translation catalogs?

The best way to validate placeholder syntax is to enforce strict automated validation scripts that check placeholder integrity, preserve brand names, and verify native orthography across all locale catalogs before deployment.

How do I set up i18next infrastructure after extracting hardcoded strings from my application?

After extracting hardcoded strings, you set up i18next infrastructure by generating locale catalogs from the extracted keys and validating that all translation files are complete and free of placeholder errors.

Why do my translation catalogs have inconsistent placeholder syntax across different locales?

Translation catalogs have inconsistent placeholder syntax because of unenforced validation during the internationalization process, which can be resolved by applying strict automated checks for placeholder integrity and native orthography.

When do I need to run an internationalization audit on my application?

You need to run an internationalization audit when preparing a software application for multi-locale deployment, ensuring all hardcoded strings are extracted and locale catalogs are complete before release.