Use AI I18N MCP

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

1. 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.
2. Read the app's package.json, package scripts, and vite.config.* as text. Do not execute the Vite config.
3. Resolve Vite root from the command's working directory. Resolve a relative aiI18n({ directory }) against that root; use an absolute directory unchanged. The default directory is i18n.
4. 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

1. List missing translations with only the resolved i18n_directory on the first call.
2. Follow every page unless the user requested a sample or narrower scope.
3. Write ordinary translations without overwriting existing non-null values.
4. Clear automatic translations or change human review values only when the user explicitly requests or approves that action.
5. 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.