Implement and test Flutter state management with Cubit and Bloc patterns.
npx skills add https://github.com/sohampawar1866/zeromile-go --skill bloc-sohampawar1866
Please help me install this Agent Skill. Skill: bloc Source: https://github.com/sohampawar1866/zeromile-go/tree/main/.agents/skills/bloc Command: npx skills add https://github.com/sohampawar1866/zeromile-go --skill bloc-sohampawar1866
High-intent search queries and answers about installing and using this skill.
Use Cubit for simple state without events, and Bloc when you need event traceability or advanced event processing like debounce and throttle via transformers. Default to Cubit and refactor to Bloc only when requirements grow.
Use the bloc_test package with mocktail to mock repositories. The blocTest function takes build, act, and expect blocks to assert emitted state sequences, and you should always call cubit.close() in tearDown.
Use sealed classes when states are mutually exclusive with subclass-specific properties and you want exhaustive switch handling. Use a single class with a status enum when states share many properties or previous data must be retained after failure.
Bloc ignores duplicate states based on equality, so emitting the same instance or an equal state triggers no rebuild. Always emit a new state object and ensure every field is included in Equatable props.
No, context.watch is only valid inside build methods. In callbacks such as onPressed, use context.read<T>() to access the bloc and dispatch events or call cubit methods.
evancaDefine a feature-first layered architecture for Flutter projects with UI, logic, and data layers.
K3vinb5Manage Cubit state and orchestrate UI side effects in Flutter apps.
aaronbassettArchitect Flutter apps with MVVM, Clean Architecture, and DI layers.
mirzadhamReviews Flutter and Dart code against library-agnostic best practice checklists.
