Update interface translations after English text changes. Find missing or outdated messages, translate them across the listed languages, preserve placeholders and plural forms, and check the results for consistency and clipped labels.
Bring the web app's interface translations up to date with its English text. Use for the periodic translation update, when `bun run i18n:status` reports missing or stale messages, or when asked to translate new UI text.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Changes add and edit English only; this update translates them into every
other interface language. Run everything from apps/web. Conventions are in
.agents/rules/web/i18n.md; wording is in src/lib/i18n/glossary.md.
git fetch origin main && git checkout -B i18n/update-<yyyy-mm-dd> origin/main.
bun run i18n:status --json lists, per language, messages that are
missing (no translation), stale (the English changed since it was
translated), or have a placeholderMismatch.t() doesn't show there. Literal labels on
menu items fail CI (tsx-menu-label-translated), but other surfaces can
slip through: labels in config objects (label: 'Foo'), sidebar and
command definitions, tab names. Read the apps/web/src diff of changes
merged since the last update
(git log --since='8 days ago' --format='%h %s' origin/main -- apps/web/src)
for user-visible text with a string literal in new UI, menus, or
navigation. Move each into src/lib/i18n/locales/en/<namespace>.ts and
render it with t(), following the rule. Leave surfaces that aren't
translated yet (most page content; the slides, canvas, spreadsheet, and
database editors) alone, so no page mixes languages.Nothing missing, stale, or newly converted: stop, without a branch or PR.
For each key, write the translation in every src/lib/i18n/locales/<language>.ts
file, in the key's namespace, in the same order as English.
grep -rn "'<namespace>.<key>'" src), not from the old translation.{{placeholders}} exactly; use the language's quotation marks.{ one, other }) is an object in
every language, with exactly the language's plural categories:
new Intl.PluralRules('<language>').resolvedOptions().pluralCategories
(Polish and Russian one, few, many, other; French, Spanish, Italian
and Portuguese add many for millions; Japanese, Korean, Chinese, Indonesian,
Vietnamese and Thai only other). The tests check the forms.bun run i18n:status --accept all, then bun run i18n:status: every
language reports up to date.bun run test -- src/lib/i18n passes (stray keys, placeholders).just test-i18n-browser passes in every language. A clipped label lists
its text: shorten that translation rather than widening the menu. The
check renders every key in the context-menu namespaces; a label in another
namespace that renders in a narrow space gets added to MENUS in
src/lib/i18n/browser-test/menus.tsx.bunx --yes @ast-grep/cli@0.44.1 scan
from the repository root, and the tests of the touched features.Commit and open a ready-for-review PR per the git skill, titled like
chore(web): update interface translations. Say which messages changed and
why (new, changed English, converted literals), and list any glossary terms
added so a native speaker can check them.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Expose new backend API endpoints through the TypeScript SDK, or record intentional exclusions. Follow existing entity and client conventions, check generated request types, and verify that each endpoint is either used by the SDK or explicitly skipped.
Add or update guided feature tours in the web app. Covers registering interface targets, writing steps, guiding users toward hidden controls, and checking the tour with saved progress and different sidebar states.
Identify the checks required for changed files, run tests, and review applicable project rules. Get a table of passed, failed, and skipped checks with evidence, helping you verify changes before handoff or pushing code.
Review and structure Rust backend changes using hexagonal architecture, which separates business rules from external interfaces. Check dependency direction, place authorization policy in domain services, and keep database operations and external clients behind defined interfaces.
Guide the integration of collaboratively edited Markdown fields into an application feature. It explains service selection, permissions inherited from parent records, content storage in Loro sessions, and how to initialize and retire each editing surface.
Add a new AI tool to an existing Rust application, from implementation and service connections to infrastructure configuration, generated TypeScript types, and a frontend component that displays the tool's results.