evanca/flutter-ai-rules / skills/flutter-best-practices
flutter-best-practices
VerifiedUse when writing, reviewing, refactoring, or planning Flutter/Dart code — screens, features, project structure, state management, folders, widgets, cubits/blocs, repositories, services, or tests.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| references/architecture-layers.md | markdown | 5.6 KB |
| references/dart-coding-practices.md | markdown | 5.5 KB |
| references/enterprise-scale.md | markdown | 6.2 KB |
| references/feature-structure.md | markdown | 6.5 KB |
| references/localization-package-boundaries.md | markdown | 3.0 KB |
references/localization-package-boundaries.md
View on GitHub# Localization and Package Boundaries
Use this when a Flutter app has app-level localization and reusable feature or
UI packages that render user-facing strings.
## Default Recommendation
Keep localization owned by the host app:
- Use Flutter gen-l10n with `flutter_localizations`, `intl`, `l10n.yaml`, and
`.arb` files in the app package.
- Expose generated app strings through an app helper such as `context.l10n`.
- Pass localized copy into reusable packages through explicit constructor
values, not by importing the app's generated localizations from the package.
- Keep package APIs dumb and portable: state in, callbacks out, labels in.
This keeps one translation surface for the product while allowing packages to
remain reusable.
## Reusable Package Pattern
For a reusable settings page, prefer a host-owned wrapper:
```dart
pkg_settings.SettingsPage(
strings: SettingsPageStrings.fromL10n(context.l10n),
themeMode: settingsState.themeMode,
locale: settingsState.locale,
supportedLocales: AppLocalizations.supportedLocales,
showLanguageSelector: AppLocalizations.supportedLocales.length > 1,
localeLabels: {
const Locale('en'): context.l10n.localeEnglish,
},
onThemeModeChanged: context.read<SettingsCubit>().setThemeMode,
onLocaleChanged: context.read<SettingsCubit>().setLocale,
onAboutTapped: () => context.push('/about'),
onLegalTapped: () => context.push('/legal'),
onLogoutTapped: context.read<AuthCubit>().logOut,
)
```
The package owns layout and interactions. The app owns localization, routing,
state management, and business behavior.
## Language Controls
Do not show a visible language picker when only one locale is supported. A
visible selector that cannot change rendered text is a no-op preference.
Recommended behavior:
- Keep locale persistence in the settings cubit or view model.
- Pass `showLanguageSelector: AppLocalizations.supportedLocales.length > 1`.
- Keep `locale: settingsState.locale` wired into `MaterialApp`.
- Add the second `.arb` file before exposing the picker.
## Very Good Open Source Pattern
Very Good Core treats localization as an app-level concern:
- The generated app structure includes `l10n.yaml`, `lib/l10n/arb`, and a
`lib/l10n/l10n.dart` helper.
- Their docs use `context.l10n` from app code after adding strings to
`lib/l10n/arb/app_en.arb`.
- Adding languages means adding new app ARB files and platform locale config.
Very Good App UI Package is described as a design-system layer that separates
UI components from business logic. Very Good Flame Game follows the same core
architecture style. Together, these examples point to app-owned localization
and package-owned reusable UI, rather than each UI package creating an
independent translation universe.
## When Package-Owned l10n Is Appropriate
Let a package ship its own ARB bundle only when it is a genuinely reusable,
published package with stable copy that should be translated independently of
the host app. For app-specific feature packages in a monorepo, host-passed
strings are usually simpler and safer.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |