Agents are good at typing and bad at taste. Agent Skills encode Flutter/Dart taste as short, task-oriented instructions your agent can load: how to add integration tests, how to set up localization, how to structure a feature.
Why skills beat a giant system prompt
- Scoped. Load only what the task needs.
- Versioned with the ecosystem. Skills ship alongside packages and docs.
- Token-cheap. The MCP tool surface was also consolidated so the agent spends budget on your code, not on boilerplate tool schemas.
How to use them day to day
- Install/configure the Dart & Flutter MCP server for your agent (Claude Code, Gemini CLI, Cursor, etc.).
- Prefer invoking an official skill over free-form “write me a login screen.”
- Keep project-local skills for house rules (folder layout, Riverpod conventions, test style).
Package skills
Pub packages can ship their own skills so an agent knows this package’s idioms, not generic Flutter. If you maintain a popular plugin, a skill is becoming part of a good developer experience — and it reduces hallucinated APIs.
Anti-patterns
- Asking one prompt to redesign architecture, add features, and write tests. Split it.
- Disabling the skill layer to “save tokens” then paying for three wrong rewrites.
Originally published on FlutterCook. Read the latest version there — that copy is the one kept up to date.
Nhận xét
Đăng nhận xét