flutter-craft

You MUST use this before any creative Flutter work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design using Clean Architecture before implementation.

Execute a Flutter implementation plan in batches with verification checkpoints

Use this to create a NEW Flutter project from scratch with Clean Architecture and Feature-Driven Development structure.

Create detailed Flutter implementation plan with bite-sized tasks following Clean Architecture layer order (Domain → Data → Presentation)

Use this agent when a major Flutter project step has been completed and needs to be reviewed against the original plan and Flutter/Dart coding standards. Examples: <example>Context: User has completed implementing a feature layer. user: "I've finished implementing the auth domain layer as outlined in task 1-3 of our plan" assistant: "Let me use the flutter-code-reviewer agent to review the implementation against our plan and Flutter best practices" <commentary>Since a major project step has been completed, use the flutter-code-reviewer agent to validate the work.</commentary></example> <example>Context: User has completed a feature with state management. user: "The AuthBloc is complete with all states and events" assistant: "Let me have the flutter-code-reviewer agent examine this implementation to ensure it follows BLoC patterns correctly" <commentary>State management implementation needs review for pattern compliance.</commentary></example>

Flutter & Dart 전문가. Use PROACTIVELY when: - Flutter 앱 개발시 - 위젯 설계 및 구현시 - 상태 관리 패턴 적용시 - 네이티브 플랫폼 연동시 - 성능 최적화 필요시

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation using Clean Architecture principles.

Use when encountering any bug, test failure, or unexpected behavior in Flutter - requires systematic investigation before proposing fixes

Use when you have a written implementation plan to execute with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of Flutter development work by presenting structured options

Use when facing 2+ independent Flutter tasks that can be worked on without shared state or sequential dependencies

Use when you have a design or requirements for a multi-step Flutter feature, before touching code

Creates a new Flutter project with Clean Architecture, domain pattern boilerplate, and production-ready setup

Use when receiving code review feedback - requires technical evaluation and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify Flutter code meets requirements

Use when executing Flutter implementation plans with independent tasks in the current session

Use when writing tests for Flutter code - follows priority-based testing (Repository → State → Widget) after implementation

Use when about to claim work is complete, fixed, or passing - requires running Flutter verification commands and confirming output before making any success claims; evidence before assertions always

Use when starting feature work that needs isolation from current workspace - creates isolated git worktrees with Flutter project setup

Use when creating new skills for flutter-craft or editing existing skills

Use when starting any conversation - establishes how to find and use Flutter development skills, requiring Skill tool invocation before ANY response including clarifying questions

1 hook across 1 event