i18n-memsource

i18n Memsource Workflow

Manages the full translation lifecycle: uploading strings to Memsource/Phrase, downloading translated files, creating PRs, and tracking status.

State

Read .cursor/skills/i18n-memsource/state.json for current sprint, version, and project ID. Update it after each upload.

Prerequisites

Memsource CLI

The memsource CLI is a Python package (memsource-cli) installed via pip3. It may not be on the default PATH. Locate and export it:

MEMSOURCE_BIN=$(python3 -c "import shutil; print(shutil.which('memsource') or '')")
if [ -z "$MEMSOURCE_BIN" ]; then
  MEMSOURCE_BIN=$(find "$HOME/Library/Python" -name memsource -type f 2>/dev/null | head -1)
fi
export PATH="$(dirname "$MEMSOURCE_BIN"):$PATH"

Authentication (credentials stay with the user)

Do not read ~/.memsourcerc, Memsource passwords, or long-lived tokens into the agent context. Phrase is a paid external service — treat credentials like any other secret.

Preferred flow:

1. Ask the user to authenticate in their own terminal and confirm memsource auth whoami works (and that MEMSOURCE_TOKEN is exported in the shell they will use for npm run memsource-*).
2. The agent may run extract/export/validation without credentials (npm run i18n, npm run export-pos, PO checks).
3. For upload/download/status, either:
   • the user runs the memsource-* / memsource job list commands themselves after the agent prepares artifacts, or
   • the user has already exported a short-lived MEMSOURCE_TOKEN in the shared shell (never paste the password into chat).

If a shared shell already has MEMSOURCE_TOKEN, verify with:

memsource auth whoami

If auth fails, stop and ask the user to refresh the token outside the agent. Also ensure jq is installed (brew install jq) — upload scripts need it.

Config

Read i18n-scripts.config.json from the project root for plugin config (languages, plugin name, language aliases, etc).