i18n-localization
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.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「i18n-localization」を使用しています。 Run i18n checker on my React project
期待される結果:
- 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.
「i18n-localization」を使用しています。 How do I set up i18n in Next.js?
期待される結果:
- 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.
「i18n-localization」を使用しています。 What are the best practices for i18n?
期待される結果:
- 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.
セキュリティ監査
安全All static findings evaluated as false positives. The skill provides i18n best practices documentation and a Python checker script. No actual security risks detected.
品質スコア
作れるもの
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
これらのプロンプトを試す
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.
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.
Explain how to add RTL (right-to-left) support for Arabic or Hebrew. Show the CSS changes needed and how to handle direction switching.
Use the i18n checker to verify that all translation keys exist across my locale JSON files. Report any missing keys per language.
ベストプラクティス
- 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
回避
- Hardcoding user-facing strings directly in components
- Concatenating translated strings with regular text
- Assuming text length stays the same across languages