Install
https://docs.flutter.dev/ai/get-startedWho it is for
If you build Flutter apps and want an AI assistant that works with a Flutter-ready set of skills, MCP settings, and rules—instead of forcing generic coding habits onto Dart/Flutter—this plugin set is a better fit. It bundles skills, MCP server settings, and rules to give a happy-path Flutter development flow and the notes that go with it.
The key part is Agent Skills: they are simple file directories, written as a complement to MCP. MCP gives the assistant dedicated tools; a Skill teaches it how to use those tools for a given task. Pure Dart work should use the other set
https://github.com/dart-lang/skills
Do not treat this repository as a stand-in for Dart language skills. You need an existing Flutter project, and you must accept installing plugins for the Agent you are actually using, following the official docs.
First try in 3 minutes
The official install path is not a local package-manager command. It is the docs page "Get started developing with AI":
https://docs.flutter.dev/ai/get-started
Follow that page to install plugins for your preferred Agent. Do not assemble an unwritten installer outside that page. Before you open the docs, confirm this is the Agent environment you want to write to, and that you are willing to change its plugin/skill settings as the page says. This changes the assistant environment; it is not a read-only look.
After install, do a low-risk check first: ask the assistant to explain how it will use Flutter Driver to talk to the app, or only explore the existing UI through MCP, and do not write test files yet. The success signal: it talks about the Flutter workflow (skills + MCP + rules) and can tell apart "explore with tools" from "turn the actions into a permanent integration test". If it starts changing pubspec or generating test files, stop it and have it repeat the paths it would change.
Usage examples
Example 1: Follow normal Flutter development. The goal of this plugin set is to extend what an AI assistant can do for Flutter development and to give tailored workflows. A task can be: in an assistant that already has the plugins, have it complete a small UI or project change using the bundled skills and rules. The available page text does not name skill folder names or specific MCP tool names. So you cannot call out a short name that never appears; what you can ask is "follow this Flutter plugin set's workflow". Still confirm paths before it edits files.
Example 2: Add integration tests, or explore the UI first. One capability is: configure Flutter Driver so it can talk to the app, and turn MCP actions into a permanent integration test. Use it when you are adding integration tests, exploring UI components through MCP, or automating a user flow with the integration_test package. The first time, prefer "explore the UI / explain what test would be generated", and only then allow MCP actions to become a permanent test. The available page text does not give a skill short name; do not invent a command name to call.
Limits
Install follows
https://docs.flutter.dev/ai/get-started
and is done for your preferred Agent. This repository does not write a second install command beside that. Dart work goes to
https://github.com/dart-lang/skills
Pull requests are not accepted right now, but feedback is welcome. The page does not give a concrete feedback form, and it does not describe uninstall steps.
Do not read "configure Flutter Driver + write MCP actions as tests" as if a copyable skill short name had already been given. The first stop is reading the docs, installing, and read-only UI exploration. Any write to integration_test, any change to driver settings, or any repo patch must first have the assistant name the files it will change; you confirm, then it continues.