builder-ui-i18n

Localize React and Next.js builder UI components by applying next-intl translations to every user-facing string, including buttons, labels, dialogs, and validation messages. This ensures English and Vietnamese screens meet localized product standards.

Yes, you can build forms in a Next.js builder app using React Hook Form, Zod, and next-safe-action patterns. This combination aligns with existing server action conventions and ensures validation patterns match the repository's standards.

Add next-intl translations to builder feature pages and toolbars by mapping every user-facing string to existing translation namespaces. This keeps tables, toolbars, and dialogs aligned with current layout and density expectations.

Yes, this Skill supports localizing empty states and validation messages in a React builder. It ensures all user-facing copy, including placeholders and form validation, uses established English and Vietnamese translation namespaces.

Localized builder UI breaks shared component conventions when forms are refactored without matching existing server action and form patterns. You must use shared components and next-safe-action patterns to maintain consistency.

Yes, you need next-intl installed to update builder screens with localized copy. The Skill requires next-intl translations in English and Vietnamese to properly implement shared UI components and validation patterns.