i18n
Skill2 starsChanged 4 months agoMITView on GitHub
Extract hardcoded user-facing strings into the project's localization system — locale files and translation calls — so the UI can be translated. Use when the user says "extract strings for translation", "internationalize this", "set up i18n", "move text to locale files", "add translation keys", or "make this translatable".
50 other projects use a version of this.
Adopted by
Most recently taken up by
- elie222/inbox-zerotheir own version, first seen Nov 15, 2026
- filipe-campos/walphtheir own version, first seen Nov 15, 2026
- haxsd/haxsd-byoktheir own version, first seen Nov 15, 2026
- lobehub/lobehubtheir own version, first seen Nov 15, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 2026
- TheBeardedBearSAS/claude-crafttheir own version, first seen Nov 11, 2026
Used with
Projects with it also use oss-pr, pr-automation and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CES-LtdSkilloss-pr
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
Also in 3 projects that use this
CES-LtdSkillpr-automation
PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".
Also in 3 projects that use this
volovelySkillpr-fix
This skill should be used when the user asks to "fix PR comments", "address PR feedback", "resolve PR comments", provides a GitHub PR URL with intent to fix, or says "pr-fix". It reads all review comments on a PR, decides which need code fixes vs. replies, makes the fixes, and posts replies — all with explicit user approval before any GitHub action.
Also in 3 projects that use this
GitHubSkillstate-management
CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.
Also in 4 projects that use this
MicrosoftSkillbump-version
Bump the VoxelPic version to a user-specified value. USE FOR: setting or updating the project version across all files that embed it. Applies to requests like 'bump version to X.Y.Z', 'set version', or 'update version'.
Also in 4 projects that use this
imehrSkillfrontend
Use when building UI components, pages, or features - guides Claude through the approved frontend stack (Next.js 15, React 19, Shadcn, Tailwind) with design-first workflow for complex UIs, enforcing patterns and quality standards
Also in 4 projects that use this
- +2 more from CES-Ltd
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- lobehub/lobe-chat★ 86ksame name
- lobehub/lobehub★ 86ksame name
- iOfficeAI/AionUi★ 34ksame name
- elie222/inbox-zero★ 13ksame name
- massCodeIO/massCode★ 7.1ksame name
- leookun/cursor-byok★ 3.2ksame name
- Pixeval/Pixeval★ 3.2ksame name
- akiver/cs-demo-manager★ 2ksame name
- d-kimuson/claude-code-viewer★ 1.3ksame name
- huoshen80/ReinaManager★ 737same name
40 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 41 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Only externalize genuine user-facing text.
- Distinctive: line 32
Keep keys stable and descriptive (by meaning/location, not by the English text) so translations survive copy edits.
- Distinctive: line 33
After extracting, report: strings extracted, keys added, locale files touched, and which locales still need real translations.
“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
i18n setup signals
!ls -d locales lang i18n public/locales src/locales translations 2>/dev/null
!grep -rilE "i18next|react-i18next|vue-i18n|formatjs|react-intl|gettext|next-intl|\\bt\\(" --include='*.*' . 2>/dev/null | grep -vE 'node_modules|\.git|dist|build' | head -15
Instructions
Extract hardcoded user-facing strings into the project's i18n system, scoped to $ARGUMENTS if a path was given. If no i18n library is set up yet, identify the idiomatic one for the stack and confirm with the user before introducing it — don't silently add a framework.
Method
- Learn the existing convention. From the signals above, find the i18n library, the locale file format (JSON/YAML/PO), the key naming scheme (nested vs flat,
feature.component.label), and how translations are called (t('key'),<FormattedMessage>,$t()). Mirror it exactly. If none exists, propose the standard for the framework and wait for confirmation. - Find the real user-facing strings. Scan the target for literal text rendered to users — JSX/template text, button labels, placeholders,
aria-labels, validation/error messages, titles. Exclude non-UI strings: log messages, code identifiers, URLs, CSS classes, test fixtures, enum keys, and config. - Replace each with a translation call using a descriptive, conventionally-named key, and add the key + original text to the default locale file. Keep interpolation intact — convert
`Hello ${name}`into the library's variable syntax (t('greeting', { name })), not a concatenation. - Handle plurals and rich text with the library's features (plural forms,
<Trans>/components for embedded markup) rather than string-splitting, which breaks in other languages. - Don't auto-translate. Populate only the default locale with the real text; add empty/placeholder entries for other existing locales (or leave them to the translation workflow) and flag that they need real translations.
Rules
- Only externalize genuine user-facing text. Leave logs, identifiers, and machine strings as literals — over-extraction is as harmful as under-extraction.
- Match the project's existing keys, file format, and call style precisely; don't invent a parallel convention.
- Preserve meaning and interpolation — never build sentences by concatenating translated fragments; word order differs across languages.
- Keep keys stable and descriptive (by meaning/location, not by the English text) so translations survive copy edits.
- After extracting, report: strings extracted, keys added, locale files touched, and which locales still need real translations. Run a build/lint to catch a missed import of the translation function.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

