Localization file sync
Your product ships in a dozen languages, and translators constantly receive strings without context — or worse, strings with broken placeholders. Design an agent that keeps localization files in sync with source strings: what it can update automatically, what it must route to human translators, and how it protects placeholders and formatting tokens. How would you verify it never corrupts a translation file, and sell the build to a team that currently does this by spreadsheet.
gate_translation_update(source_string: str, proposed_translation: str) → str["Hello {name}, you have {count} new messages","Hola {name}, tienes {count} mensajes nuevos"]out"accept"["Hello {name}","Bonjour {nom}"]out"reject_placeholder_mismatch"["Save changes",""]out"route_to_human"Turn the fuzzy goal into a bounded agent task. Say what the agent reads, what it may do on its own versus draft for a human, and what it must never touch. Then earn the trust: how you’d verify it before rollout, and the pitch (the problem, what you built, why it matters).
Agent build: design the agent in plain language (or narrate it). The coach grades the decomposition, the guardrails, the verification plan, and the pitch.