add-locale
Skill316 starsChanged 5 months agoMITView on GitHub
Use when adding a new language/locale to the application — e.g. "add language", "add locale", "new language", "new translation", "internationalization". Touches Strapi admin config, Next.js i18n routing, and translation files.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Kyome22/RunCat365their own version, first seen Oct 8, 2026
- Humanizr/Humanizertheir own version, first seen Oct 8, 2026
- polarsource/polartheir own version, first seen Oct 8, 2026
- Swttch/swttchtheir own version, first seen Oct 8, 2026
- lucasrafaldini/paperdecktheir own version, first seen Sep 30, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- polarsource/polar★ 10ksame name
- Kyome22/RunCat365★ 10ksame name
- Humanizr/Humanizer★ 9.9ksame name
- Swttch/swttch★ 322same name
- lucasrafaldini/paperdeck★ 1same name
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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-content-typeSkill
- add-ui-componentSkill
- consolidate-patternsSkill
- copy-componentSkill
- create-content-componentSkill
- find-componentSkill
- find-skillsSkill
- frontend-designSkill
- make-prSkill
- next-best-practicesSkill
- remove-azure-monitorSkill
- remove-cache-revalidationSkill
- remove-cdn-purgeSkill
- remove-sentrySkill
- resolve-review-suggestionsSkill
- review-prSkill
- seed-contentSkill
- start-workSkill
- strapi-schema-checkSkill
- validate-branch-refsSkill
- vercel-react-best-practicesSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Add a new language/locale across both apps.
- Distinctive: line 12
Ask the user for both, then validate before proceeding:
“Common” is measured: kept by at least 6 in 10 of the 5 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
Add Locale
Add a new language/locale across both apps. For the full file map and how i18n is wired, see apps/docs/docs/reference/internationalization.md.
Inputs
Ask the user for both, then validate before proceeding:
- Locale code — ISO 639-1, two lowercase letters (e.g.
de,fr,sk). Reject uppercase or invalid codes. - Locale name — capitalized, no special characters (e.g.
German).
Steps
- Translation catalog — Copy
apps/ui/locales/en.jsontoapps/ui/locales/{code}.json. Keep the keys identical; translate the values (or leave English and flag them for translation). Existing catalogs for reference:en.json,cs.json. Routing — In
apps/ui/src/lib/navigation.ts, add{code}torouting.locales, keeping the array alphabetical:locales: ["cs", "en", "{code}"],This is the only code change. The
[locale]segment,generateStaticParams, the dynamic catalog import inapps/ui/src/lib/i18n.ts, and theLocaletype (derived fromrouting.localesinapps/ui/src/types/global.d.ts) all pick up the new locale automatically.Strapi + content — these are manual; tell the user:
- Enable the locale: Strapi admin → Settings → Internationalization → Add new locale.
- Translate localized content for each i18n-enabled content type, plus single types (Navbar, Footer) and any localized seed/demo content.
See
apps/docs/docs/reference/internationalization.md(Creating Localized Content) for details.
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.

