flutter-widget-assistant

To decide between StatefulWidget and StatelessWidget, this Skill guides you through a structured interview to assess your widget's state requirements, scope, and state sharing needs. It then outputs a structured architecture spec for implementation.

The best way to structure a Flutter login screen is by applying an MVVM-style pattern with optional Riverpod integration. This Skill interviews you to determine widget scope and generates an AutoRoute, ViewModel, and UIState specification.

To manage state sharing for reusable Flutter components, this Skill evaluates your cross-screen data requirements and suggests Riverpod-based state sharing or local state alternatives. It then provides a structured implementation spec.

Yes, this architecture guidance works for both full Flutter screens and small reusable components. It applies the same structured interview flow to determine state management, widget type, and state sharing decisions across varying state requirements.

You should not use Riverpod when your widget's state requirements are strictly local and do not need cross-screen data sharing. This Skill evaluates your architecture needs and suggests local state alternatives instead of Riverpod-based sharing.