next-intl-add-language

Summary

This skill guides adding a new language to a Next.js project using the next-intl library for internationalization. It provides a structured workflow for translating message files, updating routing configuration, and integrating the new language into the UI language toggle component.

Detected Capabilities

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

Use Cases

• Add Spanish to an existing Next.js i18n application
• Support German localization with routing updates
• Expand a multilingual app to a new language region
• Implement RTL language support in next-intl projects
• Update language-specific routing and middleware for new locales

Quality Notes

• Skill assumes pre-existing project structure but does not verify it exists or describe how to create missing files
• No step-by-step guidance on translating JSON content — unclear how agent should handle missing translation keys or mismatched structures
• Does not address edge cases: RTL languages, locale code formats (e.g., en-US vs en), fallback language behavior
• No error handling guidance — what if routing.ts or middleware.ts syntax is broken after modification?
• Language toggle component integration step lacks specifics — no example of how to add language option to existing toggle
• Missing details on message file structure — are messages nested objects or flat? Are there type definitions to update?
• Does not mention testing or validation — how to verify a new language is working correctly
• Files referenced exist but skill provides minimal context on their current state or dependencies