Scaffold Flutter Architecture
Use for new feature/module boilerplate generation.
Workflow
- •Confirm target feature name and existing project state-management convention first (BLoC, Riverpod, Cubit, GetX, ValueNotifier, or clean layered default if none).
- •Create folder structure with presentation/domain/data boundaries.
- •Add state-management entry points (cubit/bloc/provider/notifier).
- •Add repository and data source contracts.
- •Add initial model/entity mapping points.
- •Add starter tests and TODOs for missing behavior.
Quality defaults
- •Keep public API small and explicit.
- •Inject dependencies through constructors.
- •Avoid hidden globals.
- •Keep files cohesive and naming consistent.
Guardrails
- •Keep scaffold minimal and compilable.
- •Avoid adding business logic before contracts/interfaces exist.
- •Do not generate unused files/classes.
Required output
- •Generated folder tree.
- •Core files created and purpose.
- •Starter tests added.
- •Remaining TODOs to complete feature behavior.