Agent skill · software engineering · madteacher
flutter-internationalization
Add, fix, audit, and maintain Flutter internationalization with gen-l10n, ARB files, AppLocalizations, flutter_localizations, intl formatting, plural/select messages, RTL support, locale-specific number/date formatting, and localization build errors. Use when asked to add l10n or i18n, translate Flutter UI text, configure l10n.yaml, manage ARB translations, migrate away from package:flutter_gen imports, or troubleshoot generated localization code.
Why this skill is useful
Provides specific workflows and configurations for Flutter internationalization that the AI wouldn't reliably generate on its own.
What it needs
Requires flutter installed locally. About 3k tokens when loaded. Last updated 2026-05-01. 104 stars on the source repository.
What this skill does
Flutter Internationalization You are a Flutter localization implementer. Make localized apps build, generate, and read naturally across target locales. Principle 0 Generated localization code must match the current Flutter project and SDK. Do not copy stale package:fluttergen imports or enable synthetic-package; use source-generated AppLocalizations imports unless the project proves it is on an older pinned Flutter workflow. Decision Guide Use gen-l10n for new work, most migrations, ARB management, plural/select messages, generated AppLocalizations, and Material/Cupertino apps. Use legacy intltranslation only when the project already uses Intl.message() plus generated messagesall.dart, or the user explicitly asks to keep that workflow. Confirm intltranslation is a dependency before running its generators. Use custom map-based localizations only for tiny prototypes or existing code that intentionally avoids code generation. Name this limitation in the final response. If the project has an existing localization setup, follow its paths, class names, locale list, and generation style before introducing defaults. Workflow 1. Inspect pubspec.yaml, l10n.yaml, existing .arb files, generated imports, MaterialApp/CupertinoApp setup, and current translation usage. 2. Identify the requested change: bootstrap l10n, add a locale, replace hardcoded UI text, add placeholders/plurals/selects, format values, fix generation, or migrate stale imports/config. 3. Use the decision guide to choose gen-l10n, legacy intltranslation, or a custom fallback. Prefer the smallest change that fits the existing project. 4. Read only the routed references needed for the task. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills madteacher/flutter-internationalization