rule-flutter-flutter-architecture-always-on

Enforce Flutter architecture by ensuring all state and orchestration are owned by controllers, leaving widgets purely for presentation. This separation prevents tangled widgets and unclear state ownership across your client app.

Manage state ownership by requiring module-scoped ownership for controllers and enforcing strict dependency injection boundaries. This approach ensures each module owns its state, preventing scope creep and architectural drift.

Govern Flutter routing by using AutoRoute with proper navigation guards. This prevents ad-hoc Navigator usage and enforces route governance, ensuring secure and consistent navigation across all modules.

Flutter projects drift from architectural tenets due to unclear state ownership and ad-hoc navigation. Enforcing widget purity, controller ownership, and route governance across modules solves this by establishing clear separation of concerns.

You should not use ad-hoc Navigator. The architecture requires AutoRoute with proper guards to enforce route governance and DI boundaries, ensuring navigation remains consistent, guarded, and testable across modules.

Yes, dependency injection is required to maintain widget purity. Enforcing DI boundaries ensures controllers own all state and orchestration, keeping widgets strictly presentation-only and preventing tangled dependencies.