flutter-localization
Skill16 starsChanged 2 months agoBSD-3-ClauseView on GitHub
Implement or review Flutter localization with gen_l10n, ARB resources, plurals, locale-aware formatting, RTL layout, and locale testing. Use for multi-language UI or localization infrastructure; not for arbitrary copy editing.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- thienqo/flutter-skillsword for word, first seen Nov 1, 2026
- johannesvedder/flutter-localization-kittheir own version, first seen Jul 30, 2026
Other versions2 projects use a version of this.
Word for word · 1
- thienqo/flutter-skills★ 16100% same
Edited · 0
None found.
Wrote their own version · 1
- johannesvedder/flutter-localization-kit★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dart-concurrencySkill
- dart-languageSkill
- flutter-accessibilitySkill
- flutter-ai-integrationSkill
- flutter-animationSkill
- flutter-app-workflowSkill
- flutter-architectureSkill
- flutter-authenticationSkill
- flutter-background-executionSkill
- flutter-build-releaseSkill
- flutter-ci-cdSkill
- flutter-code-reviewSkill
- flutter-dependency-upgradesSkill
- flutter-device-testingSkill
- flutter-figma-workflowSkill
- flutter-in-app-purchasesSkill
- flutter-mediaSkill
- flutter-navigationSkill
- flutter-networkingSkill
- flutter-notificationsSkill
- flutter-observabilitySkill
- flutter-openapi-clientSkill
- flutter-package-developmentSkill
- flutter-performanceSkill
- flutter-persistenceSkill
- flutter-platform-integrationSkill
- flutter-product-analyticsSkill
- flutter-responsive-layoutSkill
- flutter-runtime-debuggingSkill
- flutter-securitySkill
- flutter-state-managementSkill
- flutter-testingSkill
- flutter-text-renderingSkill
- flutter-ui-designSkill
- flutter-ui-patternsSkill
- flutter-visual-effectsSkill
- flutter-webviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Keep user-facing text in the project's localization pipeline and model meaning rather than concatenated fragments.
- Very specific: line 12
Read pubspec.yaml, l10n.yaml, existing ARB files, generated localization access, supported locales, and formatting packages.
- Distinctive: line 16
Use descriptive, stable message keys and document placeholders where translators need context.
- Distinctive: line 17
Use ICU plural, select, and placeholder features instead of assembling translated sentences in code.
- Distinctive: line 19
Avoid hardcoded user-facing strings, including errors, semantics labels, and empty states.
- Distinctive: line 22
Do not infer language from country or persist a locale override the user did not choose.
- Distinctive: line 28
When formatting messages or localization is in scope, follow the ICU messages and formatting reference.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flutter Localization
Keep user-facing text in the project's localization pipeline and model meaning rather than concatenated fragments.
Inspect
Read pubspec.yaml, l10n.yaml, existing ARB files, generated localization access, supported locales, and formatting packages. Preserve the established localization tool unless migration is requested.
Rules
- Use descriptive, stable message keys and document placeholders where translators need context.
- Use ICU plural, select, and placeholder features instead of assembling translated sentences in code.
- Format dates, times, numbers, currencies, and units for the active locale.
- Avoid hardcoded user-facing strings, including errors, semantics labels, and empty states.
- Let directional APIs and start/end alignment support RTL; mirror only assets whose meaning requires it.
- Define a deliberate fallback and unsupported-locale policy.
- Do not infer language from country or persist a locale override the user did not choose.
Verification
Generate localizations, analyze, and test representative locales including an RTL locale, long strings, plurals, missing resources, and locale-aware formats. Run key screens with large text because localization and layout failures often combine.
When formatting messages or localization is in scope, follow the ICU messages and formatting reference.
Sources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.