More screenshots
Works with the AI Agents you already use
next-intl: Ship Multi-Locale Next.js Without the 404s
Internationalize Next.js App Router apps with next-intl — prefixed routing, disciplined message keys, ICU plurals, hydration-safe formatting, and translation tests.
$5
next-intl: Ship Multi-Locale Next.js Without the 404s
Example session with this skill installed
Our Next.js 16 app is English-only and we need German next. Add a second locale with next-intl, prefixed routing, and CI that stops half-translated pages from shipping.
- Read your context and instructions
- Compiled the next-intl
Audit first: a pseudo-locale run in dev — every string wrapped and lengthened 40% — revealed 47 hardcoded strings, mostly in error toasts and form validation, the usual suspects. Extracted them to hierarchical keys by feature (checkout.payment.cardNumber survives redesigns; homepage.hero.button does not), with en.json as the source of truth and de.json starting as a copy marked partial. Keys are identifiers, never English strings. Routing is prefixed (/de/...), middleware matches the locale segment, and server components take the locale from params — they never guess. Plurals use ICU MessageFormat, so the cart string handles German plural rules instead of a ternary. Dates, numbers, and currencies format with the request locale on both server and client — never navigator.language directly — and time zones are explicit data, not formatting. The language switcher swaps the locale prefix on the current pathname and checks the route exists in the target locale, tested from deep pages, not just the homepage. Auto-detection runs on / only and a stored preference always beats it. CI enforces key coverage: de must have 100% of en keys before the locale ships publicly, plus a pseudo-locale layout pass on checkout and signup and screenshot review for German. The locale shipped only at 100% — a half-translated locale is worse than none, because users cannot tell which parts to trust.
Connects securely to your tools. The creator never sees your data.
About this skill
i18n fails when it is sprinkled on at the end: hardcoded strings discovered in QA, dates that break hydration, a language switcher that 404s. This skill treats locale as an architectural decision made on day one — prefixed routing chosen deliberately, message keys hierarchical by feature instead of by page, ICU MessageFormat for plurals and variables, and formatting rules that keep server and client rendering the same date. It covers the language switcher that maps the current page to the same page in the new locale, and testing translations like code: pseudo-locale in dev, key-coverage CI, and screenshot review for the long languages.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
It does not translate your copy for you — it gives you the structure that makes translation safe and testable.
ICU MessageFormat cannot fix fragments that were already concatenated; those strings have to be rewritten as single ICU strings.
Domain-based routing is the strongest SEO signal but multiplies deployment complexity; the skill recommends prefixed routing unless locales are truly separate markets.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Permissions
No special permissions declared or detected