多言語対応（i18n）

To add translations, create a translations.ts file with en/ja keys under your module, implement a get-language helper, and wire it into server and client components. This approach centralizes translation management for multilingual applications.

The best way to prevent runtime errors is to use type-safe translation keys. Structuring your translations.ts with typed keys ensures that accessing incorrect keys is caught during development rather than at runtime.

Yes, you need a translations.ts file structured with language keys under each module. This file, combined with a get-language helper, establishes a consistent usage pattern for referencing translations in both server and client components.

Yes, this approach supports English and Japanese localization. You define both en and ja keys within your translations.ts file and select the current language to access the correct keys in your components.

This method requires a consistent usage pattern across server and client components, meaning you must maintain a translations.ts file and a get-language helper manually. It currently targets English and Japanese, covering new pages and components with structured keys.