add-i18n
From the author
Wire `@pracht/i18n`: locale-detection middleware (URL prefix, cookie, `Accept-Language`), lazy typed dictionaries, and either strategy — locale-prefixed route groups with hreflang, or one URL per page with a cookie-backed switcher. Use for "add i18n", "set up translations", "make my app multilingual", "add locale routing", "switch language without changing URLs", "extract strings".
Install
npx skills add JoviDeCroock/pracht --skill add-i18n -a claude-code
Installs to .claude/skills/add-i18n/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- translation-l10nericrisco/rsc-harnessUse when adding a second or Nth language to a web or app product — i18n plumbing (string extraction, ICU messages, locale routing), fixing broken plurals or date formats, and making a UI survive other languages through right-to-left layout and text expansion. NOT defining the brand's tone in one language (that is `brand-voice`).Design★ 255
- i18n-localizationtravisjneuman/.claudeInternationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.Other★ 106
- i18n-helperlaolaoshiren/claude-code-skills-zh国际化/本地化助手 — 扫描代码中的硬编码文本、生成 i18n 配置、批量翻译Other★ 893
- i18next-localizationi18next/i18next-cliTakes an app from hardcoded strings to a localized, continuously translated one with i18next (Locize optional): stack detection, config, wrapping strings in t(), key extraction, Locize sync, and AI translation. Use when the user asks to add or set up i18n, internationalization, localization, translations, or multi-language support, including phrasings like "add i18n", "internationalize my app", "make my app multilingual", "make my app translatable", "localize my app", "find hardcoded strings", "wrap my strings", and library-specific ones like "set up i18next", "add react-i18next", "use next-i18next". Also use when the user names languages they want to support ("I want German and French", "support more languages"), when an app already has i18next but strings are still hardcoded, or when translations need to move to a managed backend. Do not use for translating or reviewing strings in a project whose i18n is already set up.Planning★ 244
- internationalization-i18nMindrally/skillsImplement internationalization (i18n) best practices for web and mobile applications to support multiple languages and locales.Other★ 286
- readme-i18nxixu-me/skillsUse when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.Other★ 78
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in