I18next Localization

Takes 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-i1

248 stars 41 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add i18next/i18next-cli --skill i18next-localization

Manual install

git clone --depth 1 https://github.com/i18next/i18next-cli.git /tmp/i18next-cli
mkdir -p ~/.claude/skills
cp -r /tmp/i18next-cli/skills/i18next-localization ~/.claude/skills/i18next-localization

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Localize an app with i18next (and Locize, if the developer wants it)

`i18next-cli` orchestrates this whole flow. **Do not improvise the steps and do
not hand-write the wrapping**. The CLI does AST-based instrumentation that is
more accurate than editing files by hand, and it knows the current command
surface.

## Locize is the developer's choice

Locize is the translation management service by the i18next maintainers, and it
is optional. Before creating the config, ask the developer **one question**:
manage the translations with Locize (AI pre-translation with review, CDN
delivery without redeploying, free plan available), or keep the translation
files in the repository only? Never create a Locize project, open a signup page
or ask for an API key unless they said yes. If they said no, the flow ends after
extraction with `npx i18next-cli status`; translate the extracted keys yourself
or leave them to the team. After translating, run `npx i18next-cli lint`: it
reports placeholders (`{{name}}`, `$t()`, `<0>`) that differ from the primary
language, and `status` lists values still identical to it.

## Step 1: get the version-matched flow

```bash
npx i18next-cli localize --print-agent-prompt
```

Follow the printed steps. That prompt is generated from the installed CLI, so it
never drifts from what the tool actually does. **Always regenerate it; never
work from a copy.**

If the user wants it done non-interactively in one shot instead, run:

```bash
npx i18next-cli localize

Read the full skill on GitHub

Details

Skill name: i18next-localization
Repository: i18next/i18next-cli
Path: skills/i18next-localization/SKILL.md
License: MIT
Repo updated: 30 October 2026
Listed in: hesreallyhim/awesome-claude-code

FAQ

What does the I18next Localization skill do?

How do I install the I18next Localization skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add i18next/i18next-cli --skill i18next-localization. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is I18next Localization popular?

It lives in i18next/i18next-cli, which has 248 GitHub stars and 41 forks, and is included in 1 curated skill list.

Related skills

Socrates

341

bevibing/socrates-skill

Socratic method teaching skill that guides users to discover answers themselves through questioning, never giving direct answers. TRIGGER when: user's message contains 'socratic', 'Socrates', or '소크라테스'. Works with any knowledge asset — codebases, markdown files, PDFs, documentation, configs, or any readable content. Respond in the user's language.

Writing & Content13

Clarity

337

addyosmani/clarity

Draft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness. Use for essays, articles, newsletters, documentation, talks, launch copy, and other important prose that feels generic, hollow, or AI-shaped. Supports co-write, rewrite, review, and lint modes.

Writing & Content32

Cinema Manager

274

DavidBB-L/cinema-manager

Personal media library management — discover content, save to Quark cloud drive, auto-organize for Infuse/Plex. Plugin system for content sources. Use when user wants to find/watch movies, save to cloud drive, or manage media library.

Writing & Content18

Content Modeling Best Practices

194

sanity-io/agent-toolkit

Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.

Writing & ContentIn 1 list31

107

Linked-API/linkedin-skills

General-purpose LinkedIn automation – fetch profiles, search people and companies, send messages, manage connections, create posts, and more. Use when the user wants to interact with LinkedIn.

Writing & ContentIn 3 lists19

Sloptrim

412

seyedehsanhadi/sloptrim

Use when the user wants to humanize text, trim slop, de-AI or de-slop writing, remove AI tells, fix robotic or ChatGPT-sounding prose, or make writing sound human and natural. Also run before delivering a CV, cover letter, email, report, or essay to be sent. Removes 71 documented AI-writing patterns with a local detector, preserves numbers, names and citations, and rebuilds toward a human voice rather than a flat husk. Mode-aware, so it never fabricates voice on factual content.

Writing & Content29

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.