i18n and localization patterns for developers
Detect hardcoded strings, manage translations, locale files and RTL support — React, Next.js and Python patterns plus a checker script
- What
- Detect hardcoded strings, manage translations, locale files and RTL support — React, Next.js and Python patterns plus a checker script
- Cost
- Free
- Needs
- a code project to internationalize; nothing else — the skill is guidance plus a checker script, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @sickn33's internationalization and localization playbook: core concepts (i18n vs l10n, locales, RTL), implementation patterns for React (react-i18next), Next.js (next-intl) and Python (gettext), a locale file-structure template, DO/DON'T best practices (translation keys, namespacing, pluralization, ICU message format, never concatenate translated strings), RTL support with CSS logical properties, a pre-ship checklist, common-issue solutions, and an `i18n_checker.py` script that detects hardcoded strings and missing translations. By @sickn33, listed here with credit to its creator. Honest caveats: a guidance playbook, not a translation service — it will not write your translations for you. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
i18n and localization patterns for developers is a free Muse playbook covering core concepts, React, Next.js, and Python patterns, a locale file template, best practices for keys, namespacing, pluralization, and ICU format, RTL support with CSS logical properties, a pre-ship checklist, and a checker script for hardcoded strings.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit b84d35aStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a code project to internationalize; nothing else — the skill is guidance plus a checker script, no accounts or keys required Install "i18n and localization patterns for developers" for me. It teaches the agent @sickn33's i18n playbook: detecting hardcoded strings, managing translation keys and locale files, React/Next.js/Python patterns, RTL support, best practices and a pre-ship checklist — plus an i18n_checker.py script that finds hardcoded strings and missing translations. MIT-licensed. Repository: https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/b84d35abf733cbbc3400dbc0e16fbbdc2a4fe97e/plugins/agentic-awesome-skills-claude/skills/i18n-localization/SKILL.md Pinned version: install the code at commit b84d35abf733cbbc3400dbc0e16fbbdc2a4fe97e exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "i18n-localization". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — point the agent at your project when you want an i18n review). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- b84d35a · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.