integrate-ai-i18n
Skill0 starsChanged 5 days agoMITView on GitHub
Integrate ai-i18n into Vite browser projects that use Vue 3, React 18+, or vanilla JavaScript and TypeScript. Use when installing or configuring @ai-i18n/vite, adding translation calls or virtual:ai-i18n imports, selecting framework mode, enabling auto imports or ESLint, configuring optional locale loading or LLM audit logs, reviewing Provider logs, or diagnosing an incomplete integration.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apply-yliu-frontend-practicesSkill
- build-mcp-appSkill
- build-mcpbSkill
- build-mcp-serverSkill
- chinese-article-writingSkill
- claude-md-improverSkill
- file-line-auditSkill
- frontend-designSkill
- git-step-commitSkill
- manage-prd-docsSkill
- modernize-ecmascriptSkill
- publish-npm-packagesSkill
- skill-creatorSkill
- skill-developmentSkill
- use-ai-i18n-mcpSkill
- use-lociSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read https://bosens-china.github.io/ai-i18n/llms.txt, select the pages that match the current framework and requested capability, and read …
- Very specific: line 23
Read the target app's package.json, vite.config.*, TypeScript config, entry files, and framework plugin setup.
- Very specific: line 30
Use one @ai-i18n/vite registration, one framework mode, and one i18n directory per Vite build.
- Distinctive: line 31
Treat reachable local workspace source as part of the consuming build.
- Very specific: line 33
If an existing overrides.json contains file-scoped rules, preserve its exact normalized POSIX paths relative to this Vite root.
- Distinctive: line 36
Do not enable optional behavior by default.
- Very specific: line 44
When the user also requests Agent-assisted translation or review, complete the Build first, then use the use-ai-i18n-mcp Skill and its …
- Distinctive: line 52
Prefer framework detection and explicit Runtime imports.
- Distinctive: line 54
Add the smallest representative translation call by following the selected framework page.
- Distinctive: line 62
Run the target app's lint, type check, relevant tests, and full Vite Build in proportion to the change.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Integrate ai-i18n
Preserve the project's package manager, Vite plugins, framework conventions, and configuration style.
Read product documentation
Read https://bosens-china.github.io/ai-i18n/llms.txt, select the pages that match the current
framework and requested capability, and read only those pages. Use llms-full.txt only when the
index or targeted pages are unavailable; do not load the full corpus by default.
User-facing installation steps, configuration fields, Runtime APIs, framework examples, generated files, and troubleshooting live in that documentation. Do not reproduce or infer those details from this Skill. If deployed documentation conflicts with the target project's installed types, source, or executable behavior, follow the target project and report the discrepancy.
Inspect the target build
Read the target app's package.json, vite.config.*, TypeScript config, entry files, and framework
plugin setup. Confirm that the app matches the current public support requirements before editing it.
In a monorepo, identify one target Vite build. Ask the user only when more than one app is plausible, or when a new setup has no source and target language decision that can be inferred from existing configuration. Preserve configured values.
Use one @ai-i18n/vite registration, one framework mode, and one i18n directory per Vite build.
Treat reachable local workspace source as part of the consuming build. Do not create a separate
integration for a source-only package or rewrite CommonJS as an incidental migration.
If an existing overrides.json contains file-scoped rules, preserve its exact normalized POSIX paths
relative to this Vite root; never rewrite them to machine-specific absolute paths during integration.
Do not enable optional behavior by default. Keep explicit imports and omit automatic translation, automatic imports, language persistence, locale loading, cache cleanup, HTML extraction, ESLint, and test integration unless the user requests them. Do not remove an optional feature that is already configured. When an optional feature is requested, read Agent defaults for optional features and the matching public documentation page.
This Skill owns package installation, Vite configuration, Runtime source integration, and integration
verification. Do not write translation or human review values as part of an integration-only task.
When the user also requests Agent-assisted translation or review, complete the Build first, then use
the use-ai-i18n-mcp Skill and its approval rules.
Apply the smallest complete setup
- Install the version required by the target repository; during the current prerelease, use the public documentation's alpha install command.
- Register the plugin in the existing Vite config without disturbing other plugins.
- Prefer framework detection and explicit Runtime imports. Override either only when the target setup or user request requires it.
- Add the smallest representative translation call by following the selected framework page.
- Integrate generated declarations and Git ignores exactly as described by the TypeScript and
generated-files pages selected from
llms.txt. - Preserve existing component style. Do not convert Vue Options API to Composition API solely for ai-i18n, and do not add React subscriptions to non-component utilities.
Verify and report
Run the target app's lint, type check, relevant tests, and full Vite Build in proportion to the change. Check installation, resolved framework mode, one Runtime translation call, generated declarations, and the resolved output directory. Verify optional features only when requested or already configured.
Report the selected app, changes made, commands run, remaining unsupported scope, and any decisions that still need user input.
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.

