i18n-next-intl-vi
Quy ước i18n (Vietnamese-first UI) với next-intl trong repo Next.js 16 này.
When & Why to Use This Skill
This Claude skill streamlines internationalization (i18n) for Next.js 16 applications using the next-intl library, specifically optimized for Vietnamese-first user interfaces. It enforces standardized coding patterns for Server and Client components, manages localized content through centralized JSON files, and ensures technical consistency by maintaining English terminology for industry-standard terms while localizing UI elements.
Use Cases
- Implementing a Vietnamese-first localization strategy in Next.js 16 projects to ensure consistent UI text management.
- Generating boilerplate code for Server Components using getTranslations and Client Components using useTranslations to follow i18n best practices.
- Refactoring hardcoded strings into centralized locale files (vi.json) to improve maintainability and multi-language support.
- Setting up locale-specific routing and layouts using setRequestLocale to enhance SEO for localized web content.
- Enforcing coding standards that prevent the use of 'use client' directives unless necessary for state or event handling within an i18n context.
| name | i18n-next-intl-vi |
|---|---|
| description | Quy ước i18n (Vietnamese-first UI) với next-intl trong repo Next.js 16 này. |
i18n (Vietnamese-first) với next-intl
Khi nào dùng skill này
- Khi thêm/sửa UI text, form labels, messages.
- Khi tạo page/layout theo locale.
Quy tắc
- UI text luôn Tiếng Việt qua
apps/web/src/i18n/locales/vi.json. - Thuật ngữ kỹ thuật giữ tiếng Anh (Next.js, React, API, RLS...).
Patterns
- Server Component:
const t = await getTranslations('namespace'). - Client Component:
const t = useTranslations('namespace'). - Page theo locale:
setRequestLocale(locale).
Không được làm
- Không hardcode English string cho UI.
- Không dùng
'use client'nếu không cần state/effect/event handlers.