ftk-l10n

Files (1)

• SKILL.md

SKILL.md (first lines)

Default locales: `id` + `en` (ask if different).

## Setup mode (no l10n yet)

1. `flutter pub add flutter_localizations --sdk flutter` and `flutter pub add intl:any` (any: flutter_localizations pins intl exactly).
2. Enable generation in `pubspec.yaml` (`flutter: generate: true`) and create `l10n.yaml`:

```yaml
arb-dir: lib/l10n
template-arb-file: app_en.arb
output-localization-file: app_localizations.dart
```

3. Create `lib/l10n/app_en.arb` and `lib/l10n/app_id.arb` with a first real string each (same keys).
4. Wire `MaterialApp`: `localizationsDelegates: AppLocalizations.localizationsDelegates`, `supportedLocales: AppLocalizations.supportedLocales`.
5. `flutter gen-l10n`, then `flutter analyze` + run a smoke check.

## Migration mode (strings → AppLocalizations)

1. Scope: one screen/feature per pass. Grep its widget files for string literals shown to users (skip logs, keys, URLs).
2. Key naming: `<feature>_<context>_<meaning>` (e.g. `login_button_submit`). Placeholders for variables, `plural` for counts — never string concatenation for sentences.
3. Every key goes into BOTH arb files in the same change; the `id` translation is real, not a copy of English (ask when unsure of wording).
4. Replace literals with `AppLocalizations.of(context)!.<key>` (or the project's established accessor), `flutter gen-l10n`, analyze, and verify the screen in both locales.

Rule: from setup onward, new user-facing strings NEVER land as hardcoded literals.

From adiwirya/flutter-tools-kit, MIT.

More from adiwirya/flutter-tools-kit