agentleFS
aymericzipaymericzip/intlayer/.agents/skills/intlayer-remix/SKILL.md

intlayer-remix

Skill863 starsChanged 13 days agoApache-2.0View on GitHub

Integrates Intlayer internationalization with Remix 3 applications. Use when the user asks to "setup Remix i18n", register the Intlayer router middleware, or use the "useIntlayer" / "useLocale" hooks in Remix route handlers and views.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

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
  1. Distinctive:

    Read content fields by name (dot access or destructuring) so the build can purge and minify the dictionary.

    line 69

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Intlayer Remix Usage

Core Philosophy

Intlayer promotes Component-Level Content Declaration. Instead of a massive global translation file, content is declared in *.content.ts files adjacent to the views that use them.

Declare Content

File: src/views/home.content.ts

import { t, type Dictionary } from "intlayer";

const content = {
  key: "home",
  content: {
    title: t({
      en: "Welcome",
      fr: "Bienvenue",
      es: "Hola",
    }),
  },
} satisfies Dictionary;

export default content;

Setup

  • Remix 3

Register the intlayer() router middleware in createRouter(), before render(). It strips the locale prefix before route matching, so routes are declared once without a :locale segment.

Hooks

useIntlayer, useDictionary and useLocale read the request locale with no argument, anywhere downstream of the middleware (route handlers and remix/component views).

import { useIntlayer, useLocale } from "remix-intlayer";

export const HomePage = () => () => {
  const { locale, availableLocales } = useLocale();
  const home = useIntlayer("home");

  return <h1>{home.title}</h1>;
};
  • useIntlayer("home", "fr") overrides the request locale for one call.
  • Remix JSX is not React: class is written as-is, and re-renders are triggered with handle.update().
  • Outside of a request, the hooks fall back to the default locale.

Bundle Optimization

Read content fields by name (dot access or destructuring) so the build can purge and minify the dictionary. Never index content at runtime (content.statuses[status], use select()), and call useIntlayer in each child component instead of passing content as a prop. See the intlayer-bundle-optimization skill.

Compiler

The Intlayer Compiler can extract all your content keys from your components, using one CLI command (npx intlayer extract) or automatically at app build.

References

Environments

  • Remix 3

Concepts

  • Variants
  • Collections
  • Compiler
  • Formatters (number, currency, date, …)

Packages

  • Intlayer Exports
  • Remix Intlayer Exports
  • remix-intlayer Intlayer
  • remix-intlayer intlayerMiddleware
  • remix-intlayer useDictionary
  • remix-intlayer useIntlayer
  • remix-intlayer useLocale

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.