Manage Localization

When To Use

Use this skill for new translation keys, language file organization, admin copy, validation messages, and repeated user-facing text.

Inputs Needed

• Feature area, language scope, reuse needs, and message ownership.

Workflow

1. Inspect existing language file structure and naming.
2. Run php artisan lang:publish before adding app-owned language files if they do not already exist.
3. Place app-owned translation files under the project’s chosen app namespace, such as lang/admin/**.
4. Centralize repeated strings into shared keys where practical.
5. Keep validation messages close to the feature or contract they support.
6. Use localized labels in Blade, Filament, Livewire, Requests, and notifications.
7. Add tests when a translation key is part of a behavior contract.