Menu
Best practices for multi-language handling, locale routing, and detection strategies across App and Pages Router. Use when adding i18n, locale routing, or language detection in Next.js.
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
| name | nextjs-i18n |
| description | Best practices for multi-language handling, locale routing, and detection strategies across App and Pages Router. Use when adding i18n, locale routing, or language detection in Next.js. |
| metadata | {"triggers":{"files":["middleware.ts","app/[lang]/**","pages/[locale]/**","messages/*.json","next.config.js"],"keywords":["i18n","locale","translation","next-intl","react-intl","next-translate"]}} |
Maintain single source of truth for locales and ensure SEO-friendly sub-path routing.
next-intl and create messages/en.json, messages/fr.json, etc.middleware.tsapp/[lang]/layout.tsx with locale paramgetMessages()hreflang tags in generateMetadatagenerateStaticParamsnext build and confirm all locale paths renderapp/[lang]/page.tsx) and i18n configuration in next.config.js for Pages Router.next-intl for App Router (modern) or react-intl / next-translate for legacy apps.middleware.ts to detect user language from Accept-Language headers or cookies and perform redirects.messages/*.json dictionaries in Server Components to keep client bundle small.hreflang tags generated correctly in metadata API for all translated routes.generateStaticParams to pre-render localized versions of static pages at build time.For detailed setup with common libraries, refer to:
getMessages().