What is the Intlayer Compiler Skill?

A step-by-step guide to set up and use the Intlayer compiler for automatic content extraction without manual .content files.

Which frameworks are supported?

Vite + React and Next.js, with framework-specific compiler docs.

Is a .content file still required?

No. If the compiler is configured, strings are extracted inline and dictionaries are generated automatically.

intlayer-compiler

Scanned

npx machina-cli add skill aymericzip/intlayer-skills/intlayer-compiler --openclaw

Files (1)

SKILL.md

1.4 KB

Intlayer Compiler Skill

The Intlayer Compiler Skill provides instructions on how to set up and use the Intlayer compiler to automatically extract content from your application.

Key Features

Automatic Content Extraction: All content will be extracted automatically from your components.
No Manual Content Files: Alleviates the need to manually create .content files.

Setup and Usage

To set up the Intlayer compiler for your project, refer to the documentation for your framework:

Once the compiler plugins are properly configured, simply write your translatable strings inline according to the framework's specifics, and the Intlayer compiler will automatically generate the dictionaries.

For more information, visit the Intlayer Compiler Architecture Documentation.

Source

git clone https://github.com/aymericzip/intlayer-skills/blob/main/skills/intlayer-compiler/SKILL.mdView on GitHub

Overview

The Intlayer Compiler Skill guides you to set up and use the Intlayer compiler to automatically extract translatable content from your app. It removes the need for manual .content files by pulling strings from your components and generating dictionaries for internationalization.

How This Skill Works

Install and configure the compiler plugins for your framework (Vite + React or Next.js). After setup, write translatable strings inline following framework conventions; the compiler scans components during builds and outputs dictionaries automatically.

When to Use It

When you want automatic extraction of translatable strings without maintaining .content files.
During a migration from manual content files to inline extraction.
When using Vite + React or Next.js and you need integrated dictionary generation.
When you need consistent dictionaries across locales with minimal configuration.
When you want to reduce localization boilerplate and streamline the i18n workflow.

Quick Start

Step 1: Install and configure the Intlayer compiler plugin for your framework.
Step 2: Write translatable strings inline in your components per framework conventions.
Step 3: Build or run your app to generate dictionaries automatically.

Best Practices

Keep translatable strings inline following your framework's conventions.
Ensure the compiler plugins are correctly configured in your project.
Run builds regularly to regenerate dictionaries after changes.
Review generated dictionaries for missing keys or locale coverage.
Consult the Intlayer documentation for architecture and environment specifics.

Example Use Cases

A Vite + React project automatically generates dictionaries from inline strings.
A Next.js app with inline translatable strings and no .content files.
An e-commerce storefront ensuring consistent i18n keys across locales.
A migration workflow moving from manual .content files to inline extraction.
A project handling pluralization and nested locales via compiler-generated dictionaries.

Frequently Asked Questions

Add this skill to your agents