菜单
Use when investigating bugs, crashes, or unexpected behavior in a Flutter app. Especially when issues involve Bloc state not emitting, null safety errors, BuildContext after async, GetIt DI failures, method channel mismatches, widget rebuilds, or memory leaks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze Jetpack Compose UI hierarchies and suggest MVVM/MVI or other architectural improvements. Use when reviewing existing Compose code, creating new Compose components, analyzing composable structure, or when the user asks about Compose architecture patterns. Best for code review and refactoring guidance.
Reviews Swift function, type, and protocol interfaces for alignment with the Swift API Design Guidelines, with emphasis on call-site clarity, naming, parameter labeling, mutability conventions, and modern async/throws patterns. Use for public APIs, reusable components, SDKs, and shared modules.
Identifies potential performance bottlenecks in Jetpack Compose code including expensive recompositions, unnecessary redraws, and memory issues. Use when code involves lists, animations, complex UI, or when the user asks about performance optimization.
Review function and class interfaces for Kotlin Coding Conventions compliance. Use when creating public APIs, reusable components, library interfaces, or when the user asks for API design review or Kotlin naming conventions.
Generic, project-abstract task workflow orchestrator. Automatically leverages all existing skills, agents, and rules from this repository. Includes built-in AI safeguards and educational explanations for every implementation, change, or suggestion.
Checks and suggests accessibility improvements for Jetpack Compose and Android Views including TalkBack labels, dynamic text support, and color contrast. Use when creating or modifying UI components, screens, or when the user asks about accessibility.
| name | flutter-bug-investigation |
| description | Use when investigating bugs, crashes, or unexpected behavior in a Flutter app. Especially when issues involve Bloc state not emitting, null safety errors, BuildContext after async, GetIt DI failures, method channel mismatches, widget rebuilds, or memory leaks. |
Foundation: Extends shared-bug-investigation with Flutter patterns.
flutter --version && grep "sdk:" pubspec.yaml
grep -r "BlocProvider\|ChangeNotifier\|GetX" lib/ # State management
# View Layer: Bloc/Cubit, widgets, state
find lib/feature/<feature>/view -name "*.dart"
# Domain Layer: Models, repository interfaces, business logic
find lib/feature/<feature>/domain -name "*.dart"
# Data Layer: DTOs, datasources, API calls
find lib/feature/<feature>/data -name "*.dart"
Debug by layer: View (Bloc emits?) → Domain (model mapping?) → Data (DTO parsing?)
// ❌ Missing emit → ✅ Add emit(LoadingState()), emit(LoadedState(data)), emit(ErrorState())
// ❌ user!.name → ✅ user?.name ?? 'Guest'
// ❌ Navigator.pop(context) after await → ✅ if (!mounted) return; Navigator.pop(context);
// ❌ Not registered → ✅ Add @injectable, run build_runner
// ❌ Wrong name → ✅ Match iOS/Android channel name
// ❌ BlocBuilder wraps Scaffold → ✅ Wrap only body
// ❌ Stream not closed → ✅ Override close(), call super.close()
| Error | Fix |
|---|---|
type 'Null' is not a subtype | Add ?? defaults |
Looking up deactivated widget | Check mounted |
Object not registered | Add @injectable, run build_runner |
MissingPluginException | Implement native iOS/Android |
setState() after dispose() | Cancel timers/streams |
RenderBox overflow | Fix constraints |
flutter analyze # Must pass (0 errors)
flutter test # All tests
flutter run --profile # Performance
flutter analyze = 0 errorsflutter test passes