React i18n migration spec
You're directing an AI agent to internationalize an existing React app: extract hardcoded strings into a message catalog, wrap them with the i18n library already in the repo, and handle pluralization and number/date formatting for an initial set of three locales. Write the spec that gets this right the first time. What does a careless 'add i18n to this app' prompt get wrong?
Implement
select_plural_categories(locale_tag: str, counts: list[int]) → list[str]Examples
in
["en",[0,1,2]]out["other","one","other"]in
["fr",[0,1,2]]out["one","one","other"]in
["pl",[1,2,5,22]]out["one","few","many","few"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.