home / skills / partme-ai / full-stack-skills / flutter
This skill helps you build Flutter apps by guiding widgets, state management, navigation, and platform integration with practical best practices.
npx playbooks add skill partme-ai/full-stack-skills --skill flutterReview the files below or copy the command above to add this skill to your agents.
---
name: flutter
description: Provides comprehensive guidance for Flutter development including widgets, state management, navigation, platform channels, and mobile app development. Use when the user asks about Flutter, needs to create Flutter applications, implement Flutter widgets, or work with Flutter features.
license: Complete terms in LICENSE.txt
---
## When to use this skill
Use this skill whenever the user wants to:
- [待完善:根据具体工具添加使用场景]
## How to use this skill
[待完善:根据具体工具添加使用指南]
## Best Practices
[待完善:根据具体工具添加最佳实践]
## Keywords
[待完善:根据具体工具添加关键词]
This skill provides practical, hands-on guidance for Flutter development across app architecture, widgets, state management, navigation, and platform integration. It helps developers design UI, manage state, implement navigation flows, and connect native platform features. Use it to accelerate building reliable cross-platform mobile apps with Flutter best practices.
The skill inspects developer goals and the Flutter problem domain, then recommends patterns, code snippets, and configuration steps tailored to the task. It explains when to use specific widgets, state management solutions (setState, Provider, Riverpod, BLoC), and navigation approaches (Navigator 2.0, go_router). It also outlines platform channel usage, testing strategies, and performance optimizations.
Which state management should I choose for a medium-sized app?
Start with Provider or Riverpod for predictable dependency injection and testability; adopt BLoC if you need strict separation and event-driven flows.
How do I debug performance issues in Flutter?
Use Flutter DevTools to profile frames, inspect the widget rebuild tree, and review memory allocation. Address expensive builds and large image allocations first.