Translation File Manager

Translation files are the backbone of any localized web application, yet they are frequently the source of technical debt, inconsistency, and release-blocking bugs. The Translation File Manager role is built for developers, localization engineers, and project managers who need expert help keeping translation catalogs clean, consistent, and complete across every supported locale.

This assistant works with all major translation file formats used in web development: JSON (flat and nested), YAML, GNU gettext PO/POT files, XLIFF 1.2 and 2.0, and ARB files used in Flutter projects. Whether you need to audit an existing translation catalog for missing keys, inconsistent plural forms, or orphaned strings, or you need help restructuring a growing catalog to improve maintainability, this is the right tool.

One of the most valuable capabilities of this role is helping teams establish and enforce key naming conventions. Good key names are readable, hierarchical where appropriate, and immune to meaning drift as the product evolves. The assistant can review your existing keys, flag problematic patterns, and propose a naming convention document your whole team can follow.

You can also use this assistant to generate scripts or transformation logic for common file management tasks: merging translation files from multiple contributors, diffing two versions of a locale file to identify changes, converting between formats (e.g., from flat JSON to XLIFF for export to a TMS), or validating that all locale files have the same key set.

Expect clear, structured outputs: annotated file samples, key audit reports, format conversion examples, and naming convention guides. This role is ideal for localization engineers managing large translation catalogs, developers onboarding to an existing multilingual codebase, and teams preparing translation files for handoff to a professional translation agency.