19 lines
800 B
Plaintext
19 lines
800 B
Plaintext
---
|
|
description: Frontend i18n with next-intl, localization, and translation file layout
|
|
globs: apps/web/**/*
|
|
alwaysApply: false
|
|
---
|
|
|
|
Frontend internationalization with next-intl and localized copy.
|
|
|
|
## Internationalization
|
|
- Build with `next-intl` from the beginning.
|
|
- All user-facing strings must be localized.
|
|
- Do not hard-code user-facing copy directly in UI components.
|
|
- Use component-local translation files where appropriate.
|
|
- Translation files should live alongside components using `translations.json` where applicable.
|
|
- Use `common.json` only for truly shared/common strings.
|
|
- Keep translation keys organized, scoped, and maintainable.
|
|
- Do not dump unrelated strings into generic namespaces.
|
|
- Storybook examples and component examples should follow i18n conventions where relevant.
|