Habilidades i18n-localization
🌍

i18n-localization

Seguro

Add Internationalization to Your App

This skill helps developers detect hardcoded strings and manage translations for multilingual applications. It provides patterns for React, Vue, and Python projects.

Suporta: Claude Codex Code(CC)
🥉 76 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "i18n-localization". Run i18n checker on my React project

Resultado esperado:

  • The checker scans your code files and locale JSONs, then reports found languages, missing translation keys, and files with hardcoded strings that need conversion to use translation keys.

A utilizar "i18n-localization". How do I set up i18n in Next.js?

Resultado esperado:

  • Use next-intl library. Create a messages folder with locale JSON files, set up the provider in your layout, and use the useTranslations hook to access translations in components.

A utilizar "i18n-localization". What are the best practices for i18n?

Resultado esperado:

  • Use translation keys instead of raw text, namespace translations by feature, support pluralization with ICU format, use Intl API for dates and numbers, and plan for RTL from the start.

Auditoria de Segurança

Seguro
v1 • 2/25/2026

All static findings evaluated as false positives. The skill provides i18n best practices documentation and a Python checker script. No actual security risks detected.

2
Arquivos analisados
402
Linhas analisadas
0
achados
1
Total de auditorias
Nenhum problema de segurança encontrado
Auditado por: claude

Pontuação de qualidade

45
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
100
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

Audit existing codebase for i18n readiness

Run the i18n checker to find hardcoded strings and missing translation keys in your codebase

Learn i18n best practices

Reference the documentation to implement proper internationalization patterns for your framework

Set up RTL language support

Configure your application for right-to-left languages using CSS logical properties

Tente Estes Prompts

Check for hardcoded strings 
Use the i18n checker script to scan my project directory for hardcoded strings. Run: python scripts/i18n_checker.py <project_path>. Analyze the results and explain what needs to be translated.
Implement React i18n 
Show me how to set up react-i18next in a React project. Include the provider setup, translation file structure, and how to use the useTranslation hook in components.
Add RTL support 
Explain how to add RTL (right-to-left) support for Arabic or Hebrew. Show the CSS changes needed and how to handle direction switching.
Check locale file consistency 
Use the i18n checker to verify that all translation keys exist across my locale JSON files. Report any missing keys per language.

Melhores Práticas

  • Use translation keys (like 'common.buttons.submit') instead of raw text strings
  • Organize translations by feature namespace (auth.json, errors.json, etc.)
  • Use CSS logical properties (margin-inline-start) for RTL compatibility

Evitar

  • Hardcoding user-facing strings directly in components
  • Concatenating translated strings with regular text
  • Assuming text length stays the same across languages

Perguntas Frequentes

What is the difference between i18n and L10n?
i18n (internationalization) is the process of making your app translatable. L10n (localization) is the actual translation work for a specific locale.
Does this skill translate strings automatically?
No, this skill detects hardcoded strings and guides you on patterns. Translation must be done manually or with separate translation services.
Which frameworks does the checker support?
The i18n_checker.py script supports React, Vue, and Python projects.
How do I handle RTL languages like Arabic?
Use CSS logical properties instead of left/right, add dir='rtl' attribute to html, and test with languages like Arabic or Hebrew.
What are translation namespaces?
Namespaces organize translations into groups like common, auth, errors. This keeps translation files manageable for large applications.
How do I handle pluralization?
Use ICU message format which supports plural rules like {count, plural, one {# item} other {# items}}

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/i18n-localization

Referência

main

Estrutura de arquivos

📁 scripts/

📄 i18n_checker.py

📄 SKILL.md