Claude Cursor opencode Skill

i18n-localization

Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download vodailocz-kilo-kit-mcp-skills_engineering_i18n-localization-0448e6c.zip · 4 KB

Install

skills CLI npx skills add https://github.com/VoDaiLocz/kilo-kit-mcp/tree/main/skills/engineering/i18n-localization
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vodailocz-kilo-kit-mcp@llmmart
Git git clone https://github.com/VoDaiLocz/kilo-kit-mcp.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vodailocz/kilo-kit-mcp collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

i18n & Localization

Internationalization (i18n) and Localization (L10n) best practices.


1. Core Concepts

Term Meaning
i18n Internationalization - making app translatable
L10n Localization - actual translations
Locale Language + Region (en-US, tr-TR)
RTL Right-to-left languages (Arabic, Hebrew)

2. When to Use i18n

Project Type i18n Needed?
Public web app ✅ Yes
SaaS product ✅ Yes
Internal tool ⚠️ Maybe
Single-region app ⚠️ Consider future
Personal project ❌ Optional

3. Implementation Patterns

React (react-i18next)

import { useTranslation } from 'react-i18next';

function Welcome() {
  const { t } = useTranslation();
  return <h1>{t('welcome.title')}</h1>;
}

Next.js (next-intl)

import { useTranslations } from 'next-intl';

export default function Page() {
  const t = useTranslations('Home');
  return <h1>{t('title')}</h1>;
}

Python (gettext)

from gettext import gettext as _

print(_("Welcome to our app"))

4. File Structure

locales/
├── en/
│   ├── common.json
│   ├── auth.json
│   └── errors.json
├── tr/
│   ├── common.json
│   ├── auth.json
│   └── errors.json
└── ar/          # RTL
    └── ...

5. Best Practices

DO ✅

  • Use translation keys, not raw text
  • Namespace translations by feature
  • Support pluralization
  • Handle date/number formats per locale
  • Plan for RTL from the start
  • Use ICU message format for complex strings

DON'T ❌

  • Hardcode strings in components
  • Concatenate translated strings
  • Assume text length (German is 30% longer)
  • Forget about RTL layout
  • Mix languages in same file

6. Common Issues

Issue Solution
Missing translation Fallback to default language
Hardcoded strings Use linter/checker script
Date format Use Intl.DateTimeFormat
Number format Use Intl.NumberFormat
Pluralization Use ICU message format

7. RTL Support

/* CSS Logical Properties */
.container {
  margin-inline-start: 1rem;  /* Not margin-left */
  padding-inline-end: 1rem;   /* Not padding-right */
}

[dir="rtl"] .icon {
  transform: scaleX(-1);
}

8. Checklist

Before shipping:

  • All user-facing strings use translation keys
  • Locale files exist for all supported languages
  • Date/number formatting uses Intl API
  • RTL layout tested (if applicable)
  • Fallback language configured
  • No hardcoded strings in components

Script

Script Purpose Command
scripts/i18n_checker.py Detect hardcoded strings & missing translations python scripts/i18n_checker.py <project_path>
Files (kilo-kit-mcp)
  • scripts
    • i18n_checker.py 7.5 KB
      Loading…
  • SKILL.md 3 KB
    ---
    name: i18n-localization
    description: Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
    allowed-tools: Read, Glob, Grep
    ---
    
    # i18n & Localization
    
    > Internationalization (i18n) and Localization (L10n) best practices.
    
    ---
    
    ## 1. Core Concepts
    
    | Term | Meaning |
    |------|---------|
    | **i18n** | Internationalization - making app translatable |
    | **L10n** | Localization - actual translations |
    | **Locale** | Language + Region (en-US, tr-TR) |
    | **RTL** | Right-to-left languages (Arabic, Hebrew) |
    
    ---
    
    ## 2. When to Use i18n
    
    | Project Type | i18n Needed? |
    |--------------|--------------|
    | Public web app | ✅ Yes |
    | SaaS product | ✅ Yes |
    | Internal tool | ⚠️ Maybe |
    | Single-region app | ⚠️ Consider future |
    | Personal project | ❌ Optional |
    
    ---
    
    ## 3. Implementation Patterns
    
    ### React (react-i18next)
    
    ```tsx
    import { useTranslation } from 'react-i18next';
    
    function Welcome() {
      const { t } = useTranslation();
      return <h1>{t('welcome.title')}</h1>;
    }
    ```
    
    ### Next.js (next-intl)
    
    ```tsx
    import { useTranslations } from 'next-intl';
    
    export default function Page() {
      const t = useTranslations('Home');
      return <h1>{t('title')}</h1>;
    }
    ```
    
    ### Python (gettext)
    
    ```python
    from gettext import gettext as _
    
    print(_("Welcome to our app"))
    ```
    
    ---
    
    ## 4. File Structure
    
    ```
    locales/
    ├── en/
    │   ├── common.json
    │   ├── auth.json
    │   └── errors.json
    ├── tr/
    │   ├── common.json
    │   ├── auth.json
    │   └── errors.json
    └── ar/          # RTL
        └── ...
    ```
    
    ---
    
    ## 5. Best Practices
    
    ### DO ✅
    
    - Use translation keys, not raw text
    - Namespace translations by feature
    - Support pluralization
    - Handle date/number formats per locale
    - Plan for RTL from the start
    - Use ICU message format for complex strings
    
    ### DON'T ❌
    
    - Hardcode strings in components
    - Concatenate translated strings
    - Assume text length (German is 30% longer)
    - Forget about RTL layout
    - Mix languages in same file
    
    ---
    
    ## 6. Common Issues
    
    | Issue | Solution |
    |-------|----------|
    | Missing translation | Fallback to default language |
    | Hardcoded strings | Use linter/checker script |
    | Date format | Use Intl.DateTimeFormat |
    | Number format | Use Intl.NumberFormat |
    | Pluralization | Use ICU message format |
    
    ---
    
    ## 7. RTL Support
    
    ```css
    /* CSS Logical Properties */
    .container {
      margin-inline-start: 1rem;  /* Not margin-left */
      padding-inline-end: 1rem;   /* Not padding-right */
    }
    
    [dir="rtl"] .icon {
      transform: scaleX(-1);
    }
    ```
    
    ---
    
    ## 8. Checklist
    
    Before shipping:
    
    - [ ] All user-facing strings use translation keys
    - [ ] Locale files exist for all supported languages
    - [ ] Date/number formatting uses Intl API
    - [ ] RTL layout tested (if applicable)
    - [ ] Fallback language configured
    - [ ] No hardcoded strings in components
    
    ---
    
    ## Script
    
    | Script | Purpose | Command |
    |--------|---------|---------|
    | `scripts/i18n_checker.py` | Detect hardcoded strings & missing translations | `python scripts/i18n_checker.py <project_path>` |
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.