Primary Flutter development workflow with GetX and Clean Architecture. Multi-agent orchestration with quality gates.
Executes Flutter development workflow with Clean Architecture and GetX patterns.
/plugin marketplace add Kaakati/rails-enterprise-dev/plugin install reactree-flutter-dev@manifest-marketplaceYou are initiating the primary Flutter development workflow powered by multi-agent orchestration with Clean Architecture and GetX.
Clean Architecture + GetX means:
.obs for reactive UI/flutter-dev [your feature request]
Authentication & Authorization:
/flutter-dev add JWT authentication with login/logout
/flutter-dev implement Google OAuth login
/flutter-dev create role-based access control
API Integration:
/flutter-dev create user management API with CRUD operations
/flutter-dev add product catalog with search and pagination
/flutter-dev implement real-time chat with WebSocket
Offline-First Features:
/flutter-dev implement offline-first notes app with sync
/flutter-dev add offline product catalog with GetStorage
/flutter-dev create cache-first user profile
State Management:
/flutter-dev add shopping cart with GetX state
/flutter-dev implement multi-step form with validation
/flutter-dev create global theme controller
When user invokes /flutter-dev [feature description], you MUST:
Example invocation:
User: /flutter-dev add user authentication with JWT
Assistant: I'll invoke the workflow orchestrator to handle this feature.
<invoke name="Task">
<parameter name="subagent_type">workflow-orchestrator</parameter>
<parameter name="description">User authentication feature</parameter>
<parameter name="prompt">
Implement user authentication feature with the following requirements:
- JWT token-based authentication
- Login and logout functionality
- Token storage with GetStorage
- Token refresh mechanism
- Protected routes
Please execute the 6-phase workflow:
1. Understand requirements
2. Inspect existing codebase patterns
3. Plan Clean Architecture implementation
4. Execute: Domain → Data → Presentation
5. Run quality gates (analyze, test, build)
6. Validate and report
Use TodoWrite for task tracking.
</parameter>
</invoke>
Remember: This command delegates to workflow-orchestrator. Do NOT implement features directly.