toolkit-i18n-operator

When to use

Use this skill when the task involves Flutter localization files generated from a CSV source of truth.

Preferred workflow

1. toolkit-i18n doctor
2. toolkit-i18n validate <csv-path> --json
3. toolkit-i18n diff <csv-path> --json
4. toolkit-i18n keys list <csv-path> --json
5. toolkit-i18n keys diff --used-file <file> --translations <csv-path> --json
6. toolkit-i18n coverage --used-file <file> --translations <csv-path> --json
7. toolkit-i18n generate <csv-path> --output <dir>

Output rules

• keep stdout compact
• prefer structured output where practical
• write generated language files to a target directory
• always report generated file paths
• dotted keys should become nested JSON objects
• compare used keys from toolkit-arch i18n-usage when available

Safety

• do not overwrite source CSV implicitly
• do not add or run live write behavior unless explicitly requested

Common prompts

• Use toolkit-i18n-operator to validate assets/i18n/translations.csv and summarize the top issues.
• Use toolkit-i18n-operator to generate localization JSON files into artifacts/i18n and report the file paths.