🎯

i18n-localization

🎯Skill

from sebas-aikon-intelligence/antigravity-awesome-skills

VibeIndex|
What it does

Detects and helps internationalize applications by identifying hardcoded strings, managing translations, and supporting multi-language and RTL language requirements.

πŸ“¦

Part of

sebas-aikon-intelligence/antigravity-awesome-skills(171 items)

i18n-localization

Installation

git cloneClone repository
git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
git cloneClone repository
git clone https://github.com/sickn33/antigravity-awesome-skills.git .claude/skills
git cloneClone repository
git clone https://github.com/sickn33/antigravity-awesome-skills.git .gemini/skills
git cloneClone repository
git clone https://github.com/sickn33/antigravity-awesome-skills.git .cursor/skills
πŸ“– Extracted from docs: sebas-aikon-intelligence/antigravity-awesome-skills
2Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

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

Overview

# 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

{t('welcome.title')}

;

}

```

Next.js (next-intl)

```tsx

import { useTranslations } from 'next-intl';

export default function Page() {

const t = useTranslations('Home');

return

{t('title')}

;

}

```

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 |