use-ai-i18n-mcp
Skill0 starsChanged 5 days agoMITView on GitHub
Use the eight local ai-i18n MCP tools to inspect missing or orphaned translations, update the configured JSON or SQLite Translation Memory, and manage reviewed overrides.json values. Use when working with ai_i18n_list_translations, ai_i18n_set_translations, ai_i18n_clear_translations, ai_i18n_list_orphan_messages, ai_i18n_delete_orphan_messages, ai_i18n_list_overrides, ai_i18n_set_overrides, or ai_i18n_delete_overrides, especially when a monorepo requires resolving one Vite app's i18n directory first.
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
- integrate-ai-i18nSkill
- manage-prd-docsSkill
- modernize-ecmascriptSkill
- publish-npm-packagesSkill
- skill-creatorSkill
- skill-developmentSkill
- 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
- Distinctive: line 8
Use the locate → list → update → verify workflow.
- Very specific: line 15
Do not load llms-full.txt by default or duplicate that guidance in this Skill.
- Very specific: line 26
Read the app's package.json, package scripts, and vite.config.* as text.
- Very specific: line 32
If more than one Vite app is plausible, ask the user which app to use before calling MCP.
- Very specific: line 35
When package installation, Vite configuration, or Runtime source integration is incomplete or requested, use the integrate-ai-i18n Skill …
- Very specific: line 41
Use tool-returned source_file values.
- Distinctive: line 43
Run the selected app's full Vite Build before first use when extraction is missing or empty, and after source, branch, or extraction …
- Distinctive: line 50
Follow every page unless the user requested a sample or narrower scope.
- Distinctive: line 51
Write ordinary translations without overwriting existing non-null values.
- Distinctive: line 56
Do not list or delete orphan messages during ordinary translation, review, or verification work.
≈ “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
Use ai-i18n MCP
Use the locate → list → update → verify workflow. Do not scan for i18n directories or edit generated files manually while the MCP tools are available.
Read the right source
For user-facing registration, product behavior, generated-file guidance, or integration
troubleshooting, read https://bosens-china.github.io/ai-i18n/llms.txt and then the one relevant page.
Do not load llms-full.txt by default or duplicate that guidance in this Skill.
For MCP calls, read Tool contracts before the first call. It is the
Agent-only authority for message identity, inputs, pagination, batch behavior, write boundaries, and
authorization. Read Error recovery only after a returned next_action is
insufficient or when a tool or protocol file is unavailable.
Locate the target app
- Identify the Vite app the user wants to change. In a monorepo, do not treat the repository root
or a similarly named
i18n/directory as the target. - Read the app's
package.json, package scripts, andvite.config.*as text. Do not execute the Vite config. - Resolve Vite
rootfrom the command's working directory. Resolve a relativeaiI18n({ directory })against that root; use an absolutedirectoryunchanged. The default directory isi18n. - Pass the resulting absolute path as
i18n_directory.
If more than one Vite app is plausible, ask the user which app to use before calling MCP.
The app's framework mode and autoImport setting affect source integration but do not change the MCP
directory contract. Do not add or remove Runtime imports as part of a translation-only MCP task.
When package installation, Vite configuration, or Runtime source integration is incomplete or
requested, use the integrate-ai-i18n Skill before starting this translation workflow.
The selected app's extracted set includes every reachable local workspace source processed by that
Vite build. Treat source-only packages as source_files within the consuming app, not as separate MCP
targets. Never point two Vite builds at one i18n directory; call the tools once per selected app.
Use tool-returned source_file values; never decode or guess a source path from a physical filename.
Run the selected app's full Vite Build before first use when extraction is missing or empty, and after source, branch, or extraction configuration changes that make it stale. Do not execute Vite config merely to locate the directory. Never open or edit Translation Memory storage directly.
Execute the workflow
- List missing translations with only the resolved
i18n_directoryon the first call. - Follow every page unless the user requested a sample or narrower scope.
- Write ordinary translations without overwriting existing non-null values.
- Clear automatic translations or change human review values only when the user explicitly requests or approves that action.
- Repeat the matching list operation to verify the result.
Do not list or delete orphan messages during ordinary translation, review, or verification work. Enter the orphan workflow only when the user explicitly requests an orphan audit or cleanup. Run one full Build first, list every requested orphan, report the retained translations, and obtain explicit user approval before deleting the listed IDs. Do not treat an earlier general cleanup request as approval after the list changes or a selected message becomes active again.
Preserve product names, intentional whitespace, and every template token. Do not guess between conflicting non-empty values.
List items omit source_files by default. Keep that compact response for translation work; request
include_source_files: true only when the user needs per-file impact or when an exact file filter must
be prepared. When message.comment and project terminology do not disambiguate short copy, request
include_occurrences: true, then read the nearby source lines for the returned files from the target
workspace. Do not request occurrences for every batch by default or treat paths and locations as write
identity for Translation Memory. For a user-approved file-scoped human review, copy exact returned
source_file values into the override update's files; never derive or shorten them. When a tool
fails, follow its returned next_action before consulting the recovery reference.
Report
Report the selected app and absolute i18n directory, added, overwritten, cleared or deleted, unchanged, remaining, and failed counts. Explain unresolved errors in the user's language without exposing internal message IDs.
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.

