AGENTS.md for Flutter
AGENTS.md for Flutter, explained
AGENTS.md is the open standard file that tells AI coding agents how to work in your repository. This page covers what a Flutter AGENTS.md should contain and how Flutter Agent Kit implements the open standard.
What is AGENTS.md?
AGENTS.md is an open, tool-agnostic markdown file that lives in your repository root and instructs AI coding agents. It emerged because every editor invented its own format (Cursor rules, Claude memory files, Copilot instructions) and teams could not share context across tools. As of September 2026 it is read by Cursor, Claude Code, opencode, GitHub Copilot, Gemini and other agents.
The idea is simple: the conventions your team enforces by code review should be written down where the agent reads them, on every task, before it writes a line.
What a Flutter AGENTS.md should contain
- Stack decisions: State management (for example Riverpod v3), routing (GoRouter), model conventions (plain Dart classes with fromJson and toJson) and why, so the agent never re-decides them.
- Architecture: Feature-first layout, where services live, how providers are organized, what belongs in a feature folder.
- Conventions: Naming, imports, error handling and what patterns to avoid (no http calls in widgets, no mixing state management).
- Setup and process: How to run and test the app (FVM, flutter test), commit and branch conventions, so the agent works the way the team works.
The negative rules matter most. Agents drift toward training-data defaults (Bloc, freezed, type-first folders) unless you tell them explicitly not to.
The limits of a single file
AGENTS.md is always loaded, so it must stay small. Deep reference material does not fit: how to wire RevenueCat entitlements, how to structure Firestore streams, how to handle push token sync.
The pattern that works is AGENTS.md for always-on rules plus on-demand docs the agent opens when a topic comes up, plus step-by-step skills per feature. That is the structure Flutter Agent Kit ships: AGENTS.md, .ai docs and 18 feature skills.
How Flutter Agent Kit implements it
- AGENTS.md, always loaded: Architecture, data, services, UI, conventions, setup, git and process, tuned for the kit's Riverpod v3 feature-first template.
- On-demand .ai docs: Deep references pulled in only when the agent needs them, keeping the always-loaded context lean.
- 18 feature skills: Each a structured workflow distilled from shipping real apps, from auth to paywalls to AI chat.
- Agent-agnostic: Works with Cursor, Claude Code, opencode, GitHub Copilot, Gemini, ChatGPT, Devin. One context layer, every agent.
Frequently asked questions
Is AGENTS.md free to use?
Yes. AGENTS.md is an open standard. Anyone can add one to a repository. What Flutter Agent Kit sells is the content: a tuned AGENTS.md, .ai docs and 18 feature skills paired with a production-tested template.
Where does AGENTS.md go in a Flutter project?
In the repository root, next to pubspec.yaml. Agents look for it there on startup and read it before each task.
Does AGENTS.md replace CLAUDE.md or .cursorrules?
It can. AGENTS.md is the cross-tool standard, and the kit ships it as the primary context layer with entry points for specific agents where useful. One file serves Cursor, Claude Code, opencode, Copilot and Gemini.
Get Flutter Agent Kit
Flutter Agent Kit ships a tuned AGENTS.md, on-demand .ai docs and 18 feature skills alongside a production-tested Riverpod v3 template, for €99.99 one-time with lifetime updates.