intlayer-config
npx machina-cli add skill aymericzip/intlayer-skills/intlayer-config --openclawIntlayer Configuration
Configure Intlayer project settings and environment variables. Check these files to identify which locales are declared for the application, which helps in defining the appropriate content.
Supported configuration files:
intlayer.config.{ts|js|json|json5|jsonc|cjs|mjs}.intlayerrc
It acts as the central brain for your application's internationalization strategy. It is divided into several specialized sections that control everything from language support to AI-powered translations.
Internationalization
This section defines your language footprint.
- Locales: Define which languages you support (e.g., English, French, Spanish).
- Default Locale: Set the fallback language if a user's preference isn't found.
Routing & middleware
Controls how users navigate between different languages.
AI & Automation
Intlayer integrates with major AI providers (OpenAI, Anthropic, Gemini, etc.) to automate your workflow.
Content & Dictionaries
Manages how and where your translation files are handled.
- Import Mode: Choose between Static (faster performance), Dynamic (lazy loading), or Fetch (live updates from a CMS).
- Auto-Transformation: Automatically convert Markdown or HTML strings into processed components.
Editor & System
Settings for the visual workflow and internal plumbing.
References
Concepts
Packages
Source
git clone https://github.com/aymericzip/intlayer-skills/blob/main/skills/intlayer-config/SKILL.mdView on GitHub Overview
Intlayer-config centralizes project settings and environment variables for Intlayer integrations. It helps you declare supported locales, set a default locale, and tune routing, AI automation, and translation handling.
How This Skill Works
It reads and writes the supported config files (intlayer.config.ts/js/json/json5/jsonc/cjs/mjs and .intlayerrc). It exposes sections for Internationalization, Routing, AI & Automation, Content & Dictionaries, and Editor settings, letting you define Locales, Default Locale, Import Mode, and Auto-Transformation.
When to Use It
- You need to declare which locales your application supports and set a sensible default locale.
- You want to tailor routing/middleware to language prefixes or URLs for multilingual navigation.
- You’re configuring how translation assets are loaded (Static, Dynamic, or Fetch) to balance performance and freshness.
- You’re enabling auto-transformation to convert strings into processed components or formats.
- You’re integrating AI providers (OpenAI, Anthropic, Gemini, etc.) to automate translations or content workflows.
Quick Start
- Step 1: Create or update intlayer.config.{ts|js|json|json5|jsonc|cjs|mjs} to declare Locales and Default Locale.
- Step 2: Choose Import Mode (Static/Dynamic/Fetch) and enable Auto-Transformation in the Content & Dictionaries section.
- Step 3: Add AI & Automation providers, test locale routing, commit changes, and monitor translations in your environment.
Best Practices
- Define explicit Locales and validate them across the app to avoid missing translations.
- Choose Import Mode based on performance needs: Static for speed, Dynamic for on-demand loading, Fetch for live updates.
- Use Auto-Transformation judiciously and test with representative strings to prevent broken components.
- Version-control all changes to intlayer.config.* and .intlayerrc; document environment-specific overrides.
- Regularly audit AI provider configurations and secret management to ensure secure access and up-to-date capabilities.
Example Use Cases
- Declare English, French, and Spanish locales with French as a non-default route and English as the default.
- Set Import Mode to Static for production apps, while enabling Dynamic for admin dashboards that edit translations.
- Configure AI & Automation to use OpenAI for translations and Gemini for glossary-driven suggestions.
- Enable routing middleware so /fr, /en, and /es prefixes route to the correct locale content.
- Enable Auto-Transformation to convert Markdown strings into processed React/Vue components during build.
