Menu
One-shot lingui extract + compile to resync the locale catalogs (Invoke when user types /i18n-sync or asks to run i18n-sync)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | i18n-sync |
| std-agent-type | commands |
| description | One-shot lingui extract + compile to resync the locale catalogs (Invoke when user types /i18n-sync or asks to run i18n-sync) |
Resync the lingui catalogs: extract new copy -> prompt for translation -> compile the runtime artifacts. Full background lives in the lingui-i18n skill.
extract:
bash .stdai/standards/skills/lingui-i18n/scripts/extract.sh
Report the Missing count per locale. If any locale other than the source locale (en) has missing translations, list the files to translate at packages/i18n/locales/<locale>/messages.po and ask the user to translate them (or confirm machine-translated placeholders).
compile:
bash .stdai/standards/skills/lingui-i18n/scripts/compile.sh
Forward $ARGUMENTS (for example --strict, which makes compile fail on untranslated messages).
Run the coverage gate and report failures:
pnpm run i18n:audit
Confirm git diff shows updated packages/i18n/locales/**/messages.mjs artifacts and remind the user to commit them together with the source change.
.po files.Design execution rules for building or reworking XID front-end surfaces (Hosted UI / console / landing / SDK components) -- produce non-templated interfaces inside the existing --xid-* design system and avoid recognizable AI-default patterns Creating a page or component, reworking a layout, writing UI copy, or when a reviewer says the interface "looks AI-generated" or "too templated"
The full lingui i18n workflow (setup / extract / translate / compile / adding a locale), with runnable scripts and ICU examples Adding or changing UI copy, adding a language, setting up lingui, catalogs out of sync, or an i18n check failing in CI
Complete execution rules for detail and motion polish on XID interfaces. Covers twelve dimensions -- alignment, spacing, typography, color contrast, interaction states, micro-interactions, motion choreography, copy, edge states, responsiveness, performance, code -- split into a brand register (landing) and a product register (Hosted UI / account / console / docs) A reviewer says the details are unfinished, final polish before shipping, filling in missing interaction states, adding or tuning motion, fixing alignment and spacing, or the last quality pass before release
Design execution rules for building or reworking XID front-end surfaces (Hosted UI / console / landing / SDK components) -- produce non-templated interfaces inside the existing --xid-* design system and avoid recognizable AI-default patterns
The full lingui i18n workflow (setup / extract / translate / compile / adding a locale), with runnable scripts and ICU examples
Complete execution rules for detail and motion polish on XID interfaces. Covers twelve dimensions -- alignment, spacing, typography, color contrast, interaction states, micro-interactions, motion choreography, copy, edge states, responsiveness, performance, code -- split into a brand register (landing) and a product register (Hosted UI / account / console / docs)