i18n-localization

Detect hardcoded strings and incomplete translations in application code.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/ag47-pt/Website --skill i18n-localization-ag47-pt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-localization
Source: https://github.com/ag47-pt/Website/tree/main/.claude/skills/i18n-localization
Command: npx skills add https://github.com/ag47-pt/Website --skill i18n-localization-ag47-pt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers eliminate localization issues by identifying hardcoded text, organizing translations, and preparing applications for multilingual experiences.

Core Features & Use Cases

  • Translation Management Guidance: Provides patterns for locale files, translation keys, pluralization, date formatting, and internationalization workflows.
  • Localization Auditing: Detects hardcoded strings and checks translation completeness across supported languages.
  • RTL Support Planning: Helps applications adapt layouts for right-to-left languages and regional formatting requirements.

Quick Start

Use the i18n-localization skill to audit my project for 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 Next.js codebase?

You can detect hardcoded strings by running an automated code scan to audit your React or Next.js application for untranslated text and incomplete translation structures, enabling proper locale management.

Does this localization auditing work with Python and Vue projects?

Yes, localization auditing applies to Python and Vue projects. The code scanning mechanism detects hardcoded strings and validates translation completeness across supported languages for web applications and SaaS products requiring multilingual support.

What is the best way to check translation completeness across locale files?

Checking translation completeness involves analyzing locale files and validating translation keys against your application code, ensuring no missing translations exist across supported languages for internationalization best practices.

How do I plan RTL support for right-to-left languages in my application?

Planning RTL support involves adapting application layouts for right-to-left languages and regional formatting requirements, ensuring proper text direction and UI alignment for multilingual experiences.

Can I get guidance on translation key patterns and pluralization for locale files?

Yes, translation management guidance provides patterns for locale files, including translation keys, pluralization, date formatting, and internationalization workflows to structure multilingual support effectively.

Why does my application code audit show incomplete translation structures?

An application code audit shows incomplete translation structures when hardcoded strings are detected and locale files lack the corresponding translation keys, indicating missing multilingual support entries across supported languages.