Flutter Expert guides Claude through Flutter and Dart work in five steps: set up the project, define state, build widgets, test and optimize. Each step has a check, such as flutter analyze, flutter test and a profile run, with a recovery action when it fails.
Six reference files cover Riverpod, Bloc and Cubit, GoRouter, widget patterns, feature-based project structure and performance.
What You Get
- Widget code with const constructors and list keys
- Riverpod providers or Bloc and Cubit classes
- GoRouter route configuration with shell routes and deep links
- Widget and integration test structure
- A feature-based project layout and a performance checklist
Common Use Cases
- Starting a Flutter app with a feature-based structure
- Choosing between Riverpod and Bloc for state
- Adding navigation with deep links and an auth guard
- Fixing dropped frames found in DevTools
What Makes It Unique
It names the habits that cause Flutter bugs: building widgets inside build(), mutating state in place, using setState for app-wide state and skipping const. The workflow ties each step to a command and a recovery path, and a troubleshooting table covers analyzer errors, async widget tests, dependency conflicts, jank and hot reload quirks.
Under The Hood
The skill is a SKILL.md with six reference files and no scripts, and the references load by topic. The workflow tells the agent to run flutter pub get, flutter analyze, flutter test with coverage and flutter run in profile mode, and the troubleshooting table suggests flutter pub upgrade. These commands install packages and write build output and coverage files in your project. The skill does not fetch web pages or call outside APIs by itself.