translations

Standardize Laravel translation keys by applying domain namespaces and consistent naming conventions across en and de locale files. Use frontmatter-driven SKILL.md rules to prevent duplication and drift between PHP arrays and JSON translation files.

Use JSON files for generic frontend-friendly labels and PHP arrays for domain-specific terms in Laravel localization. This separation ensures translation files remain organized and prevents key duplication across user-facing strings.

Test for missing translations by running MissingTranslationTest to verify coverage across en and de locales. Add new translation entries to both lang/en and lang/de files, then execute the test to ensure complete bilingual support.

Manage i18n placeholder syntax by following standardized rules for translations in Laravel projects. Consistent placeholder syntax across JSON and PHP translation files prevents runtime errors and ensures correct variable interpolation in user-facing strings.

Yes, this convention supports both JSON and PHP translation files in Laravel. It specifies usage rules for both formats, ensuring bilingual English and German support while maintaining consistent key naming and namespace conventions across the project.

Laravel translation keys drift without standardized localization rules for key naming and namespaces. Applying consistent conventions across lang files and running MissingTranslationTest prevents duplication and ensures translation coverage remains synchronized.