← ClaudeAtlas

flutter-mvvm-architecturelisted

Apply the Flutter team's official app-architecture guidelines (docs.flutter.dev/app-architecture, the MVVM pattern used by the Compass sample app) whenever writing, reviewing, refactoring, or reasoning about Flutter/Dart code. Trigger this for anything touching Flutter widgets, screens, ViewModels, state management, repositories, services, dependency injection, Provider, ChangeNotifier, Command objects, Result/error-handling types, or Flutter project/folder structure — even if the user doesn't say "architecture" or "MVVM" explicitly. Also trigger when scaffolding a new Flutter feature or screen, deciding where business logic or a network call should live, converting ad-hoc setState()/StatefulWidget logic into a layered design, adding persistence (SharedPreferences/SQL) or offline support, or auditing existing Flutter code for separation-of-concerns problems.
reza00farjam/flutter-mvvm-architecture-skill · ★ 1 · AI & Automation · score 67
Install: claude install-skill reza00farjam/flutter-mvvm-architecture-skill
# Flutter MVVM Architecture This skill encodes the Flutter team's official recommended app architecture: <https://docs.flutter.dev/app-architecture>, including the [core architecture concepts](https://docs.flutter.dev/app-architecture/concepts) (separation of concerns, single source of truth, unidirectional data flow, immutable state) summarized under "Core principles" below. It's the same architecture used in Flutter's reference sample, the [Compass app](https://github.com/flutter/samples/tree/main/compass_app). Apply it by default whenever generating or reviewing non-trivial Flutter code (more than a single throwaway widget). These are the Flutter team's recommendations, not rigid law — treat them as strong defaults, and adapt when a repo already has an established, different convention (e.g. it's already fully built on `riverpod` or `flutter_bloc`). Even then, keep the underlying principles: separation of concerns, single source of truth, unidirectional data flow, and dumb widgets. > Verified against the live docs on 2026-08-14 (site showed Flutter 3.44.7, > pages last updated May–July 2026). If `provider`, `go_router`, or `freezed` > ship a breaking major version, or docs.flutter.dev/app-architecture shows a > materially newer revision, re-check that page before trusting the > package-specific code samples in this skill. ## Why this matters Good architecture makes Flutter apps easier to maintain, test, and scale across a growing team, and it's what most production Flu