flutter-best-practices

# Flutter Best Practices Standards for building maintainable Flutter apps, distilled from the official Flutter architecture guide and LeanCode's experience shipping 40+ Flutter projects (including a 30-developer banking app). Apply these when writing new code; when touching existing code, prefer consistency with the surrounding codebase and raise conflicts with these standards rather than silently rewriting. ## How to use this skill Read the reference file that matches the task. Read more than one when tasks overlap (e.g. a new feature touches both structure and coding style). | Task | Read | |---|---| | Design layers, decide where logic lives, MVVM, repositories/services | [references/architecture-layers.md](references/architecture-layers.md) | | Create/organize a feature, folder structure, state management wiring | [references/feature-structure.md](references/feature-structure.md) | | Write or review Dart/Flutter code, widgets, tests, lints | [references/dart-coding-practices.md](references/dart-coding-practices.md) | | Multi-team/multi-package apps, monorepo, navigation, localization, API contracts, E2E tests | [references/enterprise-scale.md](references/enterprise-scale.md) | | App localization setup, reusable UI package string ownership, language picker visibility | [references/localization-package-boundaries.md](references/localization-package-boundaries.md) | For a quick task (small widget fix, one-line review comment), the core rules below may be enough on their ...