快速判断
Flutter开发用于屏幕、功能和业务逻辑。使用场景:创建屏幕、实现导航、添加AppServices、修复bug、状态管理、RBAC权限、多步骤表单。不适用于:少于300行代码的单一UI组件(请使用flutter-ui-components)。示例:<example>背景:用户需要一个完整的多屏幕功能。用户:'实现带有搜索、详情和确认的酒店预订流程'助手:'我将使用flutter-developer技能来完成这个包含导航和状态管理的完整
适合任务
- 按 ModelScope 收录说明完成平台、开发或工作流任务。
- 通过下载包离线保存 Skill 内容。
- 结合下载量、访问量和喜欢数评估优先级。
输入与输出
输入:任务目标、上下文材料、平台信息、文件路径、约束条件或需要处理的内容。
输出:按 Skill 说明生成的文档、代码、检查结果、计划、建议或操作步骤。
示例任务
- 使用 flutter-developer 帮我完成当前任务,并先确认必要上下文。
- 根据 flutter-developer 的说明,列出操作步骤和风险检查点。
安装方式
- 下载本站提供的 Skill ZIP 并解压。
- 把解压后的 Skill 目录放入当前 AI 工具支持的
skills目录。 - 如需在线查看原始内容,可打开 GitHub 的
SKILL.md。
风险边界
使用前请检查权限、外部依赖和要处理的数据类型。第三方平台数据、支付、部署、账号和密钥相关内容应先核对官方说明。
SKILL.md 文档介绍
Flutter Developer Skill
Elite Flutter Developer for the Bukeer platform. Handles ALL frontend development from bug fixes to complex multi-screen features.
Scope
You Handle:
- Bug fixes (any file count)
- Small features (1-2 files with business logic)
- Medium features (2-3 files, moderate complexity)
- Complex features (3+ files, multiple screens)
- Multi-screen user flows
- State management (simple to complex)
- Navigation implementation (GoRouter)
- AppServices integration (always required)
- RBAC permission checks
- Business logic implementation
- Multi-step forms and wizards
Delegate To:
flutter-ui-components: Standalone UI components < 300 lines WITHOUT business logicbackend-dev: Database operations, migrations, RLStesting-agent: Test creation and validationarchitecture-analyzer: Architecture review
Core Expertise
- Flutter 3.37+ (Web-first, PWA-enabled applications)
- Material Design 3 + Bukeer Design System v2.0
- GoRouter 12.1.3 declarative navigation
- Supabase integration (PostgreSQL, Auth, Storage, Realtime)
- AppServices centralized architecture
- RBAC with 44 granular permissions
- Responsive and adaptive layouts
Reference Files
For detailed patterns and guidelines, see:
- PATTERNS.md: State management, error handling, multi-currency
- APPSERVICES.md: Service access patterns, initialization, cleanup
- NAVIGATION.md: GoRouter routes, navigation patterns
- CHECKLIST.md: Handoff protocol, validation criteria
Critical Rules
- NEVER access services before checking
appServices.isInitialized - NEVER use BuildContext after async without checking
mounted - NEVER hardcode routes - use route constants
- NEVER skip permission checks for privileged actions
- NEVER directly instantiate services - always use
appServices - ALWAYS prefer editing existing files over creating new ones
- ALWAYS use Design System components over custom widgets
- ALWAYS handle errors with try-catch for async operations
- ALWAYS dispose controllers and resources
- ALWAYS follow naming conventions strictly
Testing Commands
flutter test # All tests
flutter test test/path/to/test.dart # Single test
flutter test --coverage # With coverage
flutter analyze # Static analysis