メニュー
Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo. Use when working with locize_sync.py, localization files in app/src/assets/localization/ or components/src/assets/localization/, or syncing translations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | locize-sync |
| description | Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo. Use when working with locize_sync.py, localization files in app/src/assets/localization/ or components/src/assets/localization/, or syncing translations. |
The Locize synchronization system manages internationalization (i18n) for the Opentrons monorepo. A unified Python script syncs localization files between the codebase and Locize cloud service.
Dry-Run Mode: All commands support --dry-run to preview actions without making changes.
Sync Script (scripts/locize_sync.py) — Python script executed via uv run, two actions:
push-local: Upload local English and Chinese translations to Locizedownload-remote: Download English and Chinese translations from LocizeLocalization Files
app/src/assets/localization/ — main application translationscomponents/src/assets/localization/ — shared component translationsen) is the source of truth; Chinese (zh) is downloaded from Locize. Chinese (zh) files may be invisible to agents because of the repo's ignore rules.components/ into app/ before syncing, then unconsolidates backAuthentication — LOCIZE_API_KEY and LOCIZE_PROJECT_ID env vars (local .env or GitHub Actions secrets)
uv run scripts/locize_sync.py push-local
Pushes English translations from repo to Locize. The script consolidates components/ JSON into app/, runs locize-cli sync, then unconsolidates and formats with make format-js.
When to use: After updating local English/Chinese strings, before handing to translators, to resolve drift.
uv run scripts/locize_sync.py download-remote
Downloads English and Chinese translations from Locize, overwriting local files. Consolidates, downloads, unconsolidates, and formats.
When to use: After translators finish work, prior to release, to align with remote content.
uv run scripts/locize_sync.py push-local --dry-run
uv run scripts/locize_sync.py download-remote --dry-run
Performs consolidation/unconsolidation to validate workspace, displays exact commands, but makes no remote changes.
uvx ruff check --fix scripts/locize_sync.py && uvx ruff format scripts/locize_sync.py
Store credentials in repository secrets: LOCIZE_API_KEY, LOCIZE_PROJECT_ID.
scripts/locize_sync.pyDeep-dive review of frontend diffs against Opentrons architecture, UI layers, a11y, and prop design patterns.
Conventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment. Use when working with files in opentrons-ai-server/ or discussing the AI server API.
Conventions for the analyses snapshot testing framework in analyses-snapshot-testing/. Use when working with protocol analysis snapshots, adding protocols, updating snapshots, or running snapshot tests.
Simulate and analyze Opentrons protocols to verify correctness. Use when asked to verify, simulate, analyze, validate, or check a protocol, or when needing to confirm a newly created protocol works.
CSS Modules conventions, Stylelint rules, design tokens (spacing, colors, typography, border-radius), and patterns for the Opentrons monorepo. Use when working with .module.css files or styling React components in app/, components/, protocol-visualization/, protocol-designer/, or other JS packages.
Vite demo and Playwright + Applitools tests for packed @opentrons JS packages in js-package-testing/. Covers components, shared-data, step-generation, and protocol-visualization. Use for integration testing, package linking, or visual testing.