intlayer-backend
Skill863 starsChanged 13 days agoApache-2.0View on GitHub
Integrates Intlayer internationalization with Node.js / Bun backends (Express, Fastify, Hono, NestJS, AdonisJS, Elysia, HTMX). Use when the user asks to "translate API responses", "setup server-side i18n", register the Intlayer middleware, or use "t" / "getIntlayer" in a route handler.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aymericzip/intlayer-skillsword for word, first seen Sep 30, 2026
Other versions1 project uses a version of this.
Word for word · 1
- aymericzip/intlayer-skills★ 5100% same
Edited · 0
None found.
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-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
- 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, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 19
Every backend integration works the same way:
≈ “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 Backend Usage
Core Philosophy
Every backend integration works the same way:
- A middleware / plugin (
intlayer()) resolves the locale of each request (cookie, header,Accept-Language) and scopes it to that request. - Helpers (
t,getIntlayer,getDictionary) read that request locale, so they are safe to call from services without threading a locale argument through every function.
| Framework | Package | Registration |
| Express | express-intlayer | app.use(intlayer()) |
| NestJS | express-intlayer | consumer.apply(intlayer()).forRoutes("*") |
| Fastify | fastify-intlayer | await fastify.register(intlayer) |
| Hono | hono-intlayer | app.use("*", intlayer()) |
| Elysia | elysia-intlayer | .use(intlayer()), helpers read from route intlayer |
| AdonisJS | adonis-intlayer | Registered middleware (see the AdonisJS guide) |
Declare Content
File: src/index.content.ts
import { t, type Dictionary } from "intlayer";
const content = {
key: "index",
content: {
exampleOfContent: t({
en: "Example of returned content in English",
fr: "Exemple de contenu renvoyé en français",
}),
},
} satisfies Dictionary;
export default content;Usage
Register the middleware / plugin from the table above before the routes that read content (see the Express guide), then call the helpers in any handler:
import { t, getIntlayer, getDictionary } from "express-intlayer";
import dictionaryExample from "./index.content";
app.get("/", (_req, res) => {
res.send(t({ en: "Hello", fr: "Bonjour" })); // Inline translation
});
app.get("/by-key", (_req, res) => {
res.send(getIntlayer("index").exampleOfContent); // Dictionary by key
});
app.get("/by-import", (_req, res) => {
res.send(getDictionary(dictionaryExample).exampleOfContent); // Imported dictionary
});The same helpers are exported by fastify-intlayer, hono-intlayer and adonis-intlayer. On Elysia, read them from the route context: ({ intlayer }) => intlayer!.getIntlayer("index").
For jobs, queues or emails (no incoming request), resolve content for the recipient's stored locale:
getIntlayer("index", user.locale).
References
Environments
- Express
- Fastify
- Hono
- NestJS
- AdonisJS
- Elysia
- HTMX
Concepts
- Variants
- Collections
Packages
- Intlayer Exports
- Express Intlayer Exports
- Fastify Intlayer Exports
- Hono Intlayer Exports
- Adonis Intlayer Exports
- Elysia Intlayer Exports
- adonis-intlayer intlayer
- adonis-intlayer t
- elysia-intlayer intlayer
- express-intlayer intlayer
- express-intlayer t
- fastify-intlayer intlayer
- hono-intlayer intlayer
- hono-intlayer t
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.

