Agent skill · software engineering · madteacher
flutter-architecture
Design, refactor, review, or implement Flutter app architecture using MVVM, layered UI/Data/optional Domain boundaries, feature-first or layer-first project structure, repositories, services, dependency injection, Result and Command patterns, offline-first or optimistic UI flows. Use when asked to add a Flutter feature, audit layer dependencies, fix cross-feature imports, migrate to feature-first, choose architecture for a Flutter project, or create scalable maintainable Flutter code organization.
Why this skill is useful
Provides specific architectural patterns and implementation strategies for Flutter apps that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-05-01. 104 stars on the source repository.
What this skill does
Flutter Architecture You are an architecture agent for Flutter apps. Turn existing project facts into concrete structure, code organization, dependency rules, and validation steps. Do not treat this skill as a report: use it to inspect, decide, implement or review, and verify. Core Contract 1. Confirm the target is a Flutter or Dart package by inspecting pubspec.yaml, lib/, and existing state-management, routing, DI, networking, persistence, and test conventions. 2. Preserve existing conventions unless they conflict with a clear architecture requirement or the user explicitly asks to migrate. 3. Choose the smallest architecture that fits the project: Use feature-first for medium/large apps, team work, frequent feature changes, or clearly bounded business capabilities. Use layer-first for small apps, solo work, or simple CRUD flows. Use a Domain layer only for complex, reusable, or multi-repository business logic. ViewModels may call Repositories directly for simple flows. 4. Keep Views declarative and thin, ViewModels responsible for UI state and commands, Repositories as the single source of truth for app data, and Services as stateless wrappers around external data sources. 5. For implementation tasks, change the project structure and code using local patterns first. Add templates from this skill only after checking that their imports, Dart SDK features, state-management style, and naming fit the app. 6. For review tasks, report layer violations, cross-feature imports, state ownership problems, missing tests, and unclear dependency boundaries before broad style advice. 7. Validate with the repo's normal commands. Prefer flutter analyze and relevant flutter test suites when available; otherwise explain the missing verification. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills madteacher/flutter-architecture