What problem does it solve? Flutter developers often struggle with inconsistent state management, tangled business logic in widgets, and untested Bloc/Cubit code. This Skill enforces VGV best practices for the Bloc library so your state management follows a clean, testable architecture from the start. ## Core Features & Use Cases - Cubit vs Bloc Guidance: Decision criteria for choosing Cubit or Bloc, with naming conventions for events and states using sealed classes and Equatable. - Page/View Architecture: Enforces separation where Pages provide Blocs via BlocProvider and Views consume state via BlocBuilder, BlocListener, and BlocSelector. - Testing Standards: Mandates blocTest() from package:bloc_test with package:mocktail, including mocking repositories, seeding states, and widget integration tests. - Use Case: When asked to "write tests for LoginBloc" or "add a debounced search feature", the Skill produces a Bloc with a restartable event transformer, Equatable states, and complete blocTest coverage. ## Quick Start Ask the AI to create a Bloc or Cubit for a Flutter feature, or to write blocTest unit tests for an existing Bloc class.