intlayer-compat
Skill863 starsChanged 13 days agoApache-2.0View on GitHub
Migrates an existing i18n library (i18next, react-i18next, next-intl, next-i18next, react-intl, vue-i18n, Lingui…) to Intlayer through compat adapters that keep the original API. Use when the user asks to "migrate from i18next / next-intl / vue-i18n", "keep useTranslation working", or adopt Intlayer without rewriting translation calls.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- aymericzip/intlayer-skillsedited, first seen Sep 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- aymericzip/intlayer-skills★ 599% same
Wrote their own version · 0
None found.
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 repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- .cursor/rules/commit-message-guidelines.mdCursor rule
- intlayer-angularSkill
- intlayer-astroSkill
- intlayer-backendSkill
- intlayer-bundle-optimizationSkill
- intlayer-cliSkill
- intlayer-compilerSkill
- intlayer-configSkill
- intlayer-contentSkill
- intlayer-dev-toolsSkill
- intlayer-litSkill
- intlayer-markdownSkill
- intlayer-next-jsSkill
- intlayer-preactSkill
- intlayer-reactSkill
- intlayer-remixSkill
- intlayer-remote-contentSkill
- intlayer-solidSkill
- intlayer-svelteSkill
- intlayer-usageSkill
- intlayer-vanillaSkill
- intlayer-vueSkill
- intlayer-angularSkill
- intlayer-astroSkill
- intlayer-backendSkill
- intlayer-bundle-optimizationSkill
- intlayer-cliSkill
- intlayer-compatSkill
- intlayer-compilerSkill
- intlayer-configSkill
- intlayer-contentSkill
- intlayer-dev-toolsSkill
- intlayer-litSkill
- intlayer-markdownSkill
- intlayer-next-jsSkill
- intlayer-preactSkill
- intlayer-reactSkill
- intlayer-remixSkill
- intlayer-remote-contentSkill
- intlayer-solidSkill
- intlayer-svelteSkill
- intlayer-usageSkill
- intlayer-vanillaSkill
- intlayer-vueSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 21
Run npx intlayer init --interactive: it creates intlayer.config.ts, installs the adapter and can keep existing JSON catalogs as the source …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Intlayer Compat Adapters
Compat adapters expose the exact same public API as an existing i18n library, but serve translations from Intlayer dictionaries. Application code keeps calling useTranslation, useTranslations, useIntl, $t… with keys typed against the Intlayer dictionaries.
How it works
- Run
npx intlayer init --interactive: it createsintlayer.config.ts, installs the adapter and can keep existing JSON catalogs as the source of truth via a sync plugin. - Register the adapter's bundler plugin (
<adapter>/plugin). It aliases the original imports to the adapter at build time, so no import is rewritten by hand.
Adapters
| Existing library | Adapter | Bundler plugin (<adapter>/plugin) |
i18next | @intlayer/i18next | i18nextVitePlugin |
react-i18next | @intlayer/react-i18next | reactI18nextVitePlugin |
next-i18next | @intlayer/next-i18next | createNextI18nPlugin |
next-intl | @intlayer/next-intl | createNextIntlPlugin |
use-intl | @intlayer/use-intl | useIntlVitePlugin |
react-intl | @intlayer/react-intl | reactIntlVitePlugin |
vue-i18n | @intlayer/vue-i18n | vueI18nVitePlugin |
@lingui/core, @lingui/react | @intlayer/lingui | linguiVitePlugin |
Lingui: keep the Lingui macro plugin (
@lingui/babel-plugin-lingui-macro/@lingui/swc-plugin) running before the Intlayer compiler.
Features outside translation stay with the original library, e.g.
next-intl/navigation(Link,redirect,usePathname). ICU messages (plural, select,#, formatted arguments) and rich formatting (t.rich,<Trans>) are resolved by Intlayer.
Migration guides also exist for Nuxt I18n, NGX Translate, Transloco, Svelte I18n, Next Translate, Polyglot.js and i18n-js.
Keep Existing Catalogs: Sync Plugins
To keep the current library and its message files, register a sync plugin in the plugins of intlayer.config.ts instead of (or alongside) an adapter. Intlayer then manages the catalogs (AI fill, CI tests, CMS) without changing the rendering runtime.
| Catalog format | Package | Plugins |
| JSON | @intlayer/sync-json-plugin | syncJSON, loadJSON |
| Gettext PO | @intlayer/sync-po-plugin | syncPO, loadPO |
sync*reads and writes back the files, keeping them in sync with the dictionaries.load*only loads the files into dictionaries (never writes back), e.g. for catalogs fetched from a remote source.syncJSONacceptsformat: 'intlayer' | 'icu' | 'i18next' | 'vue-i18n'to match the message syntax of the existing library.- Current scope: plain text and translations; insertions, plurals/ICU and the visual editor are not supported yet for synced files.
After migrating
Once the app runs on Intlayer, components can be moved progressively to the native API (useIntlayer + .content files) and the adapter removed.
References
Plugins
- Sync JSON
- Sync PO
Migration Guides
- Compat Adapters Overview
- i18next
- react-i18next
- next-i18next
- next-intl
- React Intl
- Vue I18n
- Lingui
- NuxtJS I18n
- NGX Translate
- Transloco
- Svelte I18n
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.

