What problem does it solve? Flutter projects often grow into tangled codebases where UI, business logic, and data access are mixed together, making features hard to find, test, and refactor. This Skill provides clear rules for organizing Flutter code into layers and features so responsibilities stay separated. ## Core Features & Use Cases - Layered Architecture Rules: Defines UI, Logic (Domain), and Data layers with strict communication rules, unidirectional data flow, and Repository as the single source of truth. - Feature-First Folder Structure: Groups all files of a feature (data, domain, ui) into one directory instead of organizing by type, with a complete sample layout. - State Management Agnostic: Applies equally to ViewModel, Cubit, Bloc, Controller, Provider, or Notifier patterns, including dependency injection wiring via constructors and a service locator. - Use Case: When adding a new profile feature to a Flutter app, follow the 7-step workflow to create the service, repository, view model, view, and DI registration in the correct layers. ## Quick Start Ask the AI to design the folder structure and layer responsibilities for a new Flutter feature such as authentication using feature-first architecture.
