@intlayer/engine 9.5.7 → 9.5.9-canary.0

package/dist/assets/installSkills/skills/dev-tools.md

@@ -0,0 +1,82 @@
+---
+name: intlayer-dev-tools
+description: Sets up Intlayer developer tooling - ESLint / oxlint rules, the Language Server (LSP), the VS Code extension, the MCP server, CI/CD automation and the Chrome extension. Use when the user asks to "lint hardcoded strings", "setup Go-to-Definition for dictionary keys", "install the Intlayer MCP", or "automate translations in CI".
+metadata:
+  author: Intlayer
+  url: https://intlayer.org
+  license: Apache-2.0
+  mcp-server: "@intlayer/mcp"
+  category: productivity
+  tags: [i18n, eslint, lsp, mcp, ci, devtools]
+  documentation: https://intlayer.org/doc
+  support: contact@intlayer.org
+---
+
+# Intlayer Dev Tools
+
+## Lint (ESLint / oxlint)
+
+`eslint-plugin-intlayer` catches hardcoded strings, dynamic calls the Intlayer compiler cannot optimize, and unused dictionary content.
+
+```bash
+npm install --save-dev eslint-plugin-intlayer
+```
+
+Then spread `intlayer.configs.recommended` in your `eslint.config.mjs` (oxlint is also supported).
+
+| Config          | `no-raw-text` | `static-dictionary-key` | `no-dynamic-field-access` |
+| --------------- | ------------- | ----------------------- | ------------------------- |
+| `recommended`   | warn          | error                   | error                     |
+| `strict`        | error         | error                   | error                     |
+| `contract-only` | off           | error                   | error                     |
+
+## Language Server (LSP)
+
+`@intlayer/lsp` (binary `intlayer-lsp`) brings Go-to-Definition from a `useIntlayer("key")` call to its `.content` file, Find References, hover previews, key autocompletion and diagnostics.
+
+```bash
+npm install --save-dev @intlayer/lsp
+```
+
+## VS Code Extension
+
+Jump from a dictionary key to its content file, extract content from a component, and run build, fill, test, push and pull from the command palette.
+
+## MCP Server
+
+Gives AI assistants access to the Intlayer documentation and CLI.
+
+```bash
+npx intlayer init mcp
+```
+
+This writes the MCP configuration for your IDE (local `@intlayer/mcp` over stdio, or the hosted `https://mcp.intlayer.org`).
+
+A WebMCP is also available for the main website and documentation at `https://intlayer.org`.
+
+## CI/CD
+
+Fill missing translations with AI on each change, and fail the build on missing ones:
+
+```bash
+npx intlayer fill --git-diff --mode complete
+npx intlayer test
+```
+
+## Chrome Extension
+
+Inspect the i18n setup of any website: framework, i18n library, locales, hreflang and SEO tags.
+
+## References
+
+- [Website](https://intlayer.org)
+- [Doc](https://intlayer.org/doc)
+
+### Tools
+
+- [ESLint Plugin](https://intlayer.org/doc/eslint.md)
+- [Language Server (LSP)](https://intlayer.org/doc/lsp.md)
+- [VS Code Extension](https://intlayer.org/doc/vs-code-extension.md)
+- [MCP Server](https://intlayer.org/doc/mcp-server.md)
+- [CI/CD](https://intlayer.org/doc/concept/ci-cd.md)
+- [Chrome Extension](https://intlayer.org/doc/chrome-extension.md)

package/dist/assets/installSkills/skills/lit.md

@@ -0,0 +1,115 @@
+---
+name: intlayer-lit
+description: Integrates Intlayer internationalization with Lit web components. Use when the user asks to "setup Lit i18n", create a translated LitElement, use the "useIntlayer" controller, or switch locale in a Lit application.
+metadata:
+  author: Intlayer
+  url: https://intlayer.org
+  license: Apache-2.0
+  mcp-server: "@intlayer/mcp"
+  category: productivity
+  tags: [i18n, lit, web-components, vite]
+  documentation: https://intlayer.org/doc
+  support: contact@intlayer.org
+---
+
+# Intlayer Lit 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 Lit elements that use them.
+
+## Workflow
+
+To create a translated element, you need two files:
+
+1.  **Declaration:** A content file (e.g., `myElement.content.ts`) defining the dictionary.
+2.  **Implementation:** A `LitElement` (e.g., `my-element.ts`) using the `useIntlayer` controller.
+
+### Declare Content
+
+Create a content file using `t()` for translations.
+**File:** `src/components/myElement.content.ts`
+
+```typescript
+import { t, type Dictionary } from "intlayer";
+
+const content = {
+  // The 'key' must be unique and matches what you pass to useIntlayer()
+  key: "my-element",
+  content: {
+    title: t({
+      en: "Welcome",
+      fr: "Bienvenue",
+      es: "Hola",
+    }),
+  },
+} satisfies Dictionary;
+
+export default content;
+```
+
+## Setup
+
+- [Vite and Lit](https://intlayer.org/doc/environment/vite-and-lit.md)
+
+Call `installIntlayer()` from `lit-intlayer` before any custom element is registered (see the [Vite and Lit guide](https://intlayer.org/doc/environment/vite-and-lit.md)).
+
+## useIntlayer Controller
+
+> [!IMPORTANT]
+> In Lit, `useIntlayer` takes the host element as first argument. It registers itself as a `ReactiveController`, so the element re-renders automatically when the locale changes.
+
+```typescript
+import { LitElement, html } from "lit";
+import { customElement } from "lit/decorators.js";
+import { useIntlayer } from "lit-intlayer";
+
+@customElement("my-element")
+export class MyElement extends LitElement {
+  private content = useIntlayer(this, "my-element");
+
+  override render() {
+    return html`
+      <h1>${this.content.title}</h1>
+      <!-- Return string (.value) for native attributes -->
+      <img alt=${this.content.title.value} />
+    `;
+  }
+}
+```
+
+## useLocale Controller
+
+```typescript
+import { useLocale } from "lit-intlayer";
+
+// Inside a LitElement
+private locale = useLocale(this);
+
+// this.locale.locale, this.locale.availableLocales, this.locale.setLocale("fr")
+```
+
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
+## References
+
+- [Website](https://intlayer.org)
+- [Doc](https://intlayer.org/doc)
+
+### Environments
+
+- [Vite and Lit](https://intlayer.org/doc/environment/vite-and-lit.md)
+- [Astro and Lit](https://intlayer.org/doc/environment/astro/lit.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
+
+### Packages
+
+- [Intlayer Exports](https://intlayer.org/doc/packages/intlayer/exports.md)

package/dist/assets/installSkills/skills/markdown.md

@@ -0,0 +1,96 @@
+---
+name: intlayer-markdown
+description: Declares and renders Markdown / rich text content with Intlayer (md(), .content.md files, MDX components, MarkdownProvider, SSR parsing). Use when the user asks to "add markdown content", "render rich text", "customize markdown components", or "render a markdown string".
+metadata:
+  author: Intlayer
+  url: https://intlayer.org
+  license: Apache-2.0
+  mcp-server: "@intlayer/mcp"
+  category: productivity
+  tags: [i18n, markdown, mdx, rich-text]
+  documentation: https://intlayer.org/doc
+  support: contact@intlayer.org
+---
+
+# Intlayer Markdown
+
+## Declaring Markdown Content
+
+```typescript
+import { file, md, t, type Dictionary } from "intlayer";
+
+const content = {
+  key: "app",
+  content: {
+    // Explicit markdown
+    intro: md("## My title \n\nLorem Ipsum"),
+    // Per-locale external files
+    article: t({
+      en: md(file("./article.en.md")),
+      fr: md(file("./article.fr.md")),
+    }),
+  },
+} satisfies Dictionary;
+
+export default content;
+```
+
+Other ways to declare it:
+
+- **`.content.md` files** (since v8.10): a Markdown file with `key` (and optional `locale`) in its front-matter, e.g. `article.en.content.md`, `article.fr.content.md`.
+- **Automatic detection**: set `contentAutoTransformation: true` (per dictionary or globally in `intlayer.config.ts`) and plain strings containing Markdown syntax are transformed.
+
+## Rendering via `useIntlayer`
+
+An `md` node renders directly as the framework's native output (JSX, VNode, HTML string). MDX is supported: component names used in the Markdown resolve against the `components` map.
+
+```tsx
+const { intro } = useIntlayer("app");
+
+<div>{intro}</div>; // Rendered markdown
+intro.use({ h1: (props) => <h1 className="title" {...props} /> }); // Local override
+intro.value; // Raw markdown string
+intro.metadata.title; // Parsed front-matter
+```
+
+Priority: `.use()` > global provider > default renderer.
+
+## Global Configuration
+
+Set default `components` and options once for the whole app:
+
+| Framework                             | Global configuration                                                  |
+| ------------------------------------- | --------------------------------------------------------------------- |
+| React, Next.js, Preact, Solid, Svelte | `MarkdownProvider` from `<package>/markdown`                          |
+| Vue                                   | `app.use(intlayerMarkdown, options)` from `vue-intlayer/markdown`     |
+| Angular                               | `createIntlayerMarkdownProvider(options)` in `ApplicationConfig`      |
+| Astro                                 | `installIntlayerMarkdown(options)` in the middleware and a `<script>` |
+| Lit, Vanilla                          | `installIntlayerMarkdown()` next to `installIntlayer()`               |
+
+## Rendering Raw Markdown Strings
+
+For Markdown that does not come from a dictionary, use the helpers from `<package>/markdown`: `<MarkdownRenderer />`, `useMarkdownRenderer()` and `renderMarkdown()`. They accept raw strings only, not `useIntlayer` nodes.
+
+## Performance
+
+- **Suspense (React)**: the parser (~55kb) is loaded lazily. Wrap components rendering Markdown in a `<Suspense>` boundary, otherwise React suspends at the root.
+- **SSR**: call `parseMarkdown()` on the server and pass the serializable AST to the client; every rendering helper accepts it, so the browser skips parsing.
+
+## Options
+
+Accepted by the global configuration and the helpers: `forceBlock`, `forceInline`, `tagfilter` (default `true`, strips dangerous HTML), `preserveFrontmatter`, `components`, `wrapper`, `renderMarkdown`.
+
+## References
+
+- [Website](https://intlayer.org)
+- [Doc](https://intlayer.org/doc)
+
+### Concepts
+
+- [Markdown](https://intlayer.org/doc/concept/content/markdown.md)
+- [HTML](https://intlayer.org/doc/concept/content/html.md)
+- [File](https://intlayer.org/doc/concept/content/file.md)
+
+### Packages
+
+- [React Intlayer MarkdownRenderer](https://intlayer.org/doc/packages/react-intlayer/MarkdownRenderer.md)

package/dist/assets/installSkills/skills/next-js.md

@@ -53,59 +53,32 @@ export default content;
 - [Next.js](https://intlayer.org/doc/environment/nextjs.md)
 - [Next.js 14](https://intlayer.org/doc/environment/nextjs/14.md)
 - [Next.js 15](https://intlayer.org/doc/environment/nextjs/15.md)
-- [No Locale Path](https://intlayer.org/doc/environment/nextjs/no-locale-path.md)
 - [Page Router](https://intlayer.org/doc/environment/nextjs/next-with-page-router.md)
 
-## Server Components
+## Provider
 
-To use Intlayer in Server Components, use `IntlayerServerProvider` to provide the locale and `useIntlayer` from `next-intlayer/server`.
+Mount one `IntlayerProvider` (from `next-intlayer/server`) in the `[locale]` layout. It serves both server and client components, so pages don't wrap themselves (see the [Next.js guide](https://intlayer.org/doc/environment/nextjs.md)).
 
-```tsx
-import { IntlayerServerProvider, useIntlayer } from "next-intlayer/server";
-
-const MyServerComponent = () => {
-  const content = useIntlayer("my-component");
-  return (
-    <div>
-      <h1>{content.text}</h1>
-    </div>
-  );
-};
-
-const Page = async ({ params }) => {
-  const { locale } = await params;
-  return (
-    <IntlayerServerProvider locale={locale}>
-      <MyServerComponent />
-    </IntlayerServerProvider>
-  );
-};
-
-export default Page;
-```
-
-## Client Components
+## useIntlayer Hook
 
-For Client Components, add the `"use client"` directive and use `useIntlayer` from `next-intlayer`. Ensure the component is wrapped in an `IntlayerClientProvider`.
+`next-intlayer` is isomorphic: the same `useIntlayer` import works in Server Components and in `"use client"` components.
 
 ```tsx
-"use client";
-
 import { useIntlayer } from "next-intlayer";
 
-export const MyClientComponent = () => {
+export const MyComponent = () => {
   const content = useIntlayer("my-component");
 
-  return (
-    <div>
-      <h1>{content.text}</h1>
-    </div>
-  );
+  return <h1>{content.text}</h1>;
 };
 ```
 
 [Next.js package Documentation](https://intlayer.org/doc/packages/next-intlayer/exports.md)
 
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
 ## References
 
 - [Website](https://intlayer.org)
@@ -116,8 +89,16 @@ export const MyClientComponent = () => {
 - [Next.js](https://intlayer.org/doc/environment/nextjs.md)
 - [Next.js 14](https://intlayer.org/doc/environment/nextjs/14.md)
 - [Next.js 15](https://intlayer.org/doc/environment/nextjs/15.md)
-- [Next.js No Locale Path](https://intlayer.org/doc/environment/nextjs/no-locale-path.md)
 - [Next.js with Page Router](https://intlayer.org/doc/environment/nextjs/next-with-page-router.md)
+- [Intlayer with next-intl](https://intlayer.org/doc/next-intl.md)
+- [Intlayer with next-i18next](https://intlayer.org/doc/next-i18next.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
 
 ### Packages
 
@@ -128,3 +109,5 @@ export const MyClientComponent = () => {
 - [Next Intlayer useDictionary](https://intlayer.org/doc/packages/next-intlayer/useDictionary.md)
 - [Next Intlayer useIntlayer](https://intlayer.org/doc/packages/next-intlayer/useIntlayer.md)
 - [Next Intlayer useLocale](https://intlayer.org/doc/packages/next-intlayer/useLocale.md)
+- [next-intlayer usePathname](https://intlayer.org/doc/packages/next-intlayer/usePathname.md)
+- [next-intlayer useRewriteURL](https://intlayer.org/doc/packages/next-intlayer/useRewriteURL.md)

package/dist/assets/installSkills/skills/preact.md

@@ -73,11 +73,29 @@ const MyComponent = () => {
 };
 ```
 
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
 ## References
 
 - [Website](https://intlayer.org)
 - [Doc](https://intlayer.org/doc)
 
+### Environments
+
 - [Vite and Preact](https://intlayer.org/doc/environment/vite-and-preact.md)
+- [Astro and Preact](https://intlayer.org/doc/environment/astro/preact.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
+
+### Packages
+
 - [Intlayer Exports](https://intlayer.org/doc/packages/intlayer/exports.md)
 - [Preact Intlayer Exports](https://intlayer.org/doc/packages/preact-intlayer/exports.md)
+- [preact-intlayer usePathname](https://intlayer.org/doc/packages/preact-intlayer/usePathname.md)

package/dist/assets/installSkills/skills/react.md

@@ -49,17 +49,15 @@ const content = {
 export default content;
 ```
 
-# Intlayer React Usage
-
 ## Setup
 
 - [Vite and React](https://intlayer.org/doc/environment/vite-and-react.md)
 - [Create React App](https://intlayer.org/doc/environment/create-react-app.md)
 - [React Router v7](https://intlayer.org/doc/environment/vite-and-react/react-router-v7.md)
-- [React Router v7 (fs routes)](https://intlayer.org/doc/environment/vite-and-react/react-router-v7-fs-routes.md)
 - [Tanstack Start](https://intlayer.org/doc/environment/tanstack-start.md)
 - [React Native and Expo](https://intlayer.org/doc/environment/react-native-and-expo.md)
 - [Lynx and React](https://intlayer.org/doc/environment/lynx-and-react.md)
+- [Storybook](https://intlayer.org/doc/storybook.md)
 
 ## useIntlayer Hook
 
@@ -80,6 +78,10 @@ const MyComponent = () => {
 };
 ```
 
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
 ## References
 
 - [Website](https://intlayer.org)
@@ -90,7 +92,18 @@ const MyComponent = () => {
 - [Vite and React](https://intlayer.org/doc/environment/vite-and-react.md)
 - [Create React App](https://intlayer.org/doc/environment/create-react-app.md)
 - [Vite and React (React Router v7)](https://intlayer.org/doc/environment/vite-and-react/react-router-v7.md)
-- [Vite and React (React Router v7 FS Routes)](https://intlayer.org/doc/environment/vite-and-react/react-router-v7-fs-routes.md)
+- [Tanstack Start](https://intlayer.org/doc/environment/tanstack-start.md)
+- [React Native and Expo](https://intlayer.org/doc/environment/react-native-and-expo.md)
+- [Lynx and React](https://intlayer.org/doc/environment/lynx-and-react.md)
+- [Astro and React](https://intlayer.org/doc/environment/astro/react.md)
+- [Storybook](https://intlayer.org/doc/storybook.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
 
 ### Packages
 
@@ -103,3 +116,7 @@ const MyComponent = () => {
 - [React Intlayer useI18n](https://intlayer.org/doc/packages/react-intlayer/useI18n.md)
 - [React Intlayer useIntlayer](https://intlayer.org/doc/packages/react-intlayer/useIntlayer.md)
 - [React Intlayer useLocale](https://intlayer.org/doc/packages/react-intlayer/useLocale.md)
+- [lynx-intlayer Exports](https://intlayer.org/doc/packages/lynx-intlayer/exports.md)
+- [react-intlayer usePathname](https://intlayer.org/doc/packages/react-intlayer/usePathname.md)
+- [react-intlayer useRewriteURL](https://intlayer.org/doc/packages/react-intlayer/useRewriteURL.md)
+- [react-native-intlayer Exports](https://intlayer.org/doc/packages/react-native-intlayer/exports.md)

package/dist/assets/installSkills/skills/remix.md

@@ -0,0 +1,95 @@
+---
+name: intlayer-remix
+description: 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.
+metadata:
+  author: Intlayer
+  url: https://intlayer.org
+  license: Apache-2.0
+  mcp-server: "@intlayer/mcp"
+  category: productivity
+  tags: [i18n, remix]
+  documentation: https://intlayer.org/doc
+  support: contact@intlayer.org
+---
+
+# 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`
+
+```typescript
+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](https://intlayer.org/doc/environment/remix-3.md)
+
+Register the `intlayer()` [router middleware](https://intlayer.org/doc/packages/remix-intlayer/intlayerMiddleware.md) 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/ui` views).
+
+```tsx
+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.
+
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
+## References
+
+- [Website](https://intlayer.org)
+- [Doc](https://intlayer.org/doc)
+
+### Environments
+
+- [Remix 3](https://intlayer.org/doc/environment/remix-3.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
+
+### Packages
+
+- [Intlayer Exports](https://intlayer.org/doc/packages/intlayer/exports.md)
+- [Remix Intlayer Exports](https://intlayer.org/doc/packages/remix-intlayer/exports.md)
+- [remix-intlayer Intlayer](https://intlayer.org/doc/packages/remix-intlayer/Intlayer.md)
+- [remix-intlayer intlayerMiddleware](https://intlayer.org/doc/packages/remix-intlayer/intlayerMiddleware.md)
+- [remix-intlayer useDictionary](https://intlayer.org/doc/packages/remix-intlayer/useDictionary.md)
+- [remix-intlayer useIntlayer](https://intlayer.org/doc/packages/remix-intlayer/useIntlayer.md)
+- [remix-intlayer useLocale](https://intlayer.org/doc/packages/remix-intlayer/useLocale.md)

package/dist/assets/installSkills/skills/remote-content.md

@@ -1,5 +1,5 @@
 ---
-name: intlayer-cms
+name: intlayer-remote-content
 description: Manages remote content and server-side dictionaries using the Intlayer CMS. Use when the user asks to "fetch remote translations", "use Intlayer CMS", or "handle server-side content".
 metadata:
   author: Intlayer

package/dist/assets/installSkills/skills/solid.md

@@ -1,5 +1,5 @@
 ---
-name: intlayer-solid-js
+name: intlayer-solid
 description: Integrates Intlayer internationalization with SolidJS components. Use when the user asks to "setup SolidJS i18n", create a new translated component, use the "useIntlayer" hook in Solid, or configure providers.
 metadata:
   author: Intlayer
@@ -51,6 +51,8 @@ export default content;
 ## Setup
 
 - [Vite and Solid](https://intlayer.org/doc/environment/vite-and-solid.md)
+- [SolidStart](https://intlayer.org/doc/environment/solid-start.md)
+- [TanStack Start and Solid](https://intlayer.org/doc/environment/tanstack-start/solid.md)
 
 ## useIntlayer Hook
 
@@ -76,6 +78,10 @@ const MyComponent = () => {
 };
 ```
 
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
 ## References
 
 - [Website](https://intlayer.org)
@@ -84,7 +90,21 @@ const MyComponent = () => {
 ### Environments
 
 - [Vite and Solid](https://intlayer.org/doc/environment/vite-and-solid.md)
+- [SolidStart](https://intlayer.org/doc/environment/solid-start.md)
+- [TanStack Start and Solid](https://intlayer.org/doc/environment/tanstack-start/solid.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
 
 ### Packages
 
 - [Solid Intlayer Exports](https://intlayer.org/doc/packages/solid-intlayer/exports.md)
+- [solid-intlayer IntlayerProvider](https://intlayer.org/doc/packages/solid-intlayer/IntlayerProvider.md)
+- [solid-intlayer useIntlayer](https://intlayer.org/doc/packages/solid-intlayer/useIntlayer.md)
+- [solid-intlayer useLocale](https://intlayer.org/doc/packages/solid-intlayer/useLocale.md)
+- [solid-intlayer usePathname](https://intlayer.org/doc/packages/solid-intlayer/usePathname.md)
+- [solid-intlayer useRewriteURL](https://intlayer.org/doc/packages/solid-intlayer/useRewriteURL.md)

package/dist/assets/installSkills/skills/svelte.md

@@ -73,12 +73,33 @@ In Svelte, `useIntlayer` returns a **store**. You must use the `$` prefix to acc
 </div>
 ```
 
+## Compiler
+
+The [Intlayer Compiler](https://intlayer.org/doc/compiler.md) can extract all your content keys from your components, using one CLI command (`npx intlayer extract`) or automatically at app build.
+
+It activates once `compiler.enabled` and `compiler.output` are set: `.svelte` files additionally require `@intlayer/svelte-compiler`.
+
 ## References
 
 - [Website](https://intlayer.org)
 - [Doc](https://intlayer.org/doc)
 
-- [Intlayer Exports](https://intlayer.org/doc/packages/intlayer/exports.md)
+### Environments
+
 - [Vite and Svelte](https://intlayer.org/doc/environment/vite-and-svelte.md)
 - [SvelteKit](https://intlayer.org/doc/environment/sveltekit.md)
+- [Astro and Svelte](https://intlayer.org/doc/environment/astro/svelte.md)
+
+### Concepts
+
+- [Variants](https://intlayer.org/doc/concept/variants.md)
+- [Collections](https://intlayer.org/doc/concept/collections.md)
+- [Compiler](https://intlayer.org/doc/compiler.md)
+- [Formatters (number, currency, date, …)](https://intlayer.org/doc/formatters.md)
+
+### Packages
+
+- [Intlayer Exports](https://intlayer.org/doc/packages/intlayer/exports.md)
 - [Svelte Intlayer Exports](https://intlayer.org/doc/packages/svelte-intlayer/exports.md)
+- [svelte-intlayer usePathname](https://intlayer.org/doc/packages/svelte-intlayer/usePathname.md)
+- [svelte-intlayer useRewriteURL](https://intlayer.org/doc/packages/svelte-intlayer/useRewriteURL.md)