Architecture Auditor

To enforce clean architecture in a Flutter project, audit feature modules to verify strict separation into presentation, domain, and data layers. This ensures UI code contains no business logic and repositories remain decoupled from UI context.

The correct folder structure for a Flutter feature module organizes code into /features/feature_name/presentation/, /features/feature_name/domain/, and /features/feature_name/data/ directories. This structure enforces strict clean architecture boundaries.

To check Riverpod best practices in a Flutter app, audit the codebase to enforce strict mode. This verifies explicit typing, checks recommended Notifier usage, and ensures no business logic resides directly inside the UI build methods.

Your Flutter architecture audit fails because making HTTP calls directly from UI components violates clean architecture separation of concerns. All network data fetching must be moved to the data layer repositories to pass the architectural smell test.

Yes, you can use an architecture audit to detect overly long build methods in Flutter. The audit includes a smell test that flags excessively long build methods to enforce UI simplicity and maintain strict separation of concerns.