Standardizes Next.js translation workflows with next-intl and build-time validation.
npx skills add https://github.com/SylphxAI/flow --skill i18n-sylphxai
Please help me install this Agent Skill. Skill: i18n Source: https://github.com/SylphxAI/flow/tree/main/.claude/skills/i18n Command: npx skills add https://github.com/SylphxAI/flow --skill i18n-sylphxai
Internationalization for Next.js apps is often ad-hoc and brittle. This Skill ensures centralized localization, avoids hard-coded strings, and enables scalable translations across routes.
Set up i18n for a Next.js project using next-intl, create locale files for your supported languages, and enforce no hard-coded strings and build-time translation checks.
High-intent search queries and answers about installing and using this skill.
Next.js i18n with next-intl involves configuring locale routing, creating translation bundles per language, and integrating next-intl middleware. This Skill standardizes that workflow by enforcing namespace-scoped bundles, server-friendly translation loading, and strict build-time validation to catch missing keys before deployment.
Hard-coded strings prevent scalable localization and create maintenance debt across routes. Centralizing translations through namespace-scoped bundles ensures every UI string is managed in one place, enabling consistent updates and reducing the risk of untranslated content reaching users.
Yes, build-time validation fails the build when translation keys are missing, guaranteeing UI integrity before production. This Skill enforces that check across all locale files, ensuring no incomplete translations slip through and every supported locale has complete coverage.
Locale management requires organizing translations into folder structures per language and establishing proper redirection rules. This Skill creates locale folders, defines routing constraints (such as preventing '/en/*' routes), and ensures seamless locale switching without hard-coded redirects.
Ad-hoc i18n is brittle, fragmented across files, and prone to untranslated strings. Standardized workflows centralize translations, enforce build-time checks, and establish consistent routing—reducing bugs and scaling cleanly as you add languages.
Yes, build-time validation requires a configured build step that checks translation key consistency across locales. This Skill integrates validation into the Next.js build pipeline so missing keys surface immediately, preventing broken deployments.
ajayatwal1105-emersonConfigure multilingual brand settings in profile.json with language codes and formatting rules.
aivos-xieDeploys/manages self-hosted Docker services like AList, Uptime Kuma, Memos for local use.
ngxtmImplement Next.js i18n with sub-path routing and middleware locale detection.
ayiaManage translation keys across seven locales with consistency validation.
