Using litei18n

Skill Aevum-Technology/litei18n-skills/skills/using-litei18n

Agent skills for LiteI18n MCP and OTA localization workflows

Install

npx -y skills add Aevum-Technology/litei18n-skills --skill using-litei18n

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when managing LiteI18n translations, localization keys, drafts, commits, releases, OTA runtime delivery, LiteI18n MCP tools, API token setup, or troubleshooting LiteI18n app translation updates

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.0 KB, as published. Nobody here has run it

Using LiteI18n

Overview

Use this as the single entry point for LiteI18n client work. It covers two connected jobs: managing translation content through MCP and integrating OTA release files into customer apps.

First Decision

Identify the task before acting:

User intent	Read
MCP setup, token errors, tool choice, permissions	`references/mcp-tool-contracts.md`
Create, edit, delete, commit, or release translations through MCP	`references/mcp-workflows.md` and `references/quality-safety.md`
Add LiteI18n OTA to an app or choose release URLs	`references/ota-runtime-integration.md`
Explain draft -> commit -> release, CDN paths, latest/versioned behavior	`references/release-pipeline.md`
Broad changes, destructive changes, token handling, retry decisions	`references/quality-safety.md`
Maintain or verify this skill's behavioral coverage	`references/scenario-pressure-tests.md`

If a live MCP tool response ever conflicts with this guidance, trust the tool's current behavior and report the drift so these references can be updated.

Core Mental Model

LiteI18n uses this pipeline:

Edit -> Draft -> Commit -> Release -> CDN/runtime consumption

Drafts are staged changes. They are not live.
Commits make drafts live inside LiteI18n.
Releases compile committed translations into public JSON files.
Apps only see OTA changes after release file generation.

Non-Negotiables

Never ask the user to paste API tokens into chat. Tokens belong in MCP client config or environment variables.
Start MCP sessions with list_projects unless the user already gave a current project id and permission context.
Use list_keys before creating or editing keys. Avoid duplicate keys and stale assumptions.
Treat create_key translations and upsert_draft writes as drafts until commit_drafts succeeds.
Confirm destructive operations, broad commits, and releases unless the user explicitly requested that exact action.
Use latest/all.json for one payload containing every locale, latest/{locale}.json for lazy per-locale loading, and v{version}/... paths for deterministic app versions.
Keep runtime fallbacks. OTA fetch failures should not break app startup, route rendering, or language switching.

Typical MCP Flow

list_projects to choose project, languages, and confirm token permissions.
list_keys with search, key id, tags, or language filters.
create_key, upsert_draft, delete_key, or restore_key.
list_keys again for affected keys to review live and draft state.
commit_drafts with a clear message when the user wants changes live.
create_release only when the user wants OTA/CDN delivery.
list_releases after release creation or release troubleshooting.

Typical OTA Flow

Confirm project slug, Supabase URL, app i18n library, supported locales, and fallback expectations.
Choose payload shape:
- latest/all.json: one startup fetch, all locales in one nested object.
- latest/{locale}.json: smaller locale-specific fetches.
- v{version}/all.json or v{version}/{locale}.json: pinned release behavior.
Merge OTA values over bundled or cached messages.
On failure, keep bundled/default/cached messages and log a non-fatal warning.
Verify by fetching the expected JSON URL and changing a released string without redeploying the app.

Quality Bar

Good LiteI18n work is idempotent, permission-aware, and auditable. Agents should inspect state before writes, use exact project and key ids, respect batch limits, produce clear commit messages, avoid blind retries, and explain recovery paths when release generation or CDN delivery fails.

Maintainers should keep references/scenario-pressure-tests.md aligned with the references and run the validators after changing this skill.