agentleFS
ZAidBinAsifZAidBinAsif/flutter-ai-starter/AGENTS.md

flutter-ai-starter

AGENTS.md0 starsChanged 5 months agoMITView on GitHub

Agent-native Flutter starter. Keep changes minimal, verified, and aligned with the repository contract. Run the single gate before calling work done: This runs format, analyze, build_runner, tests with coverage, coverage threshold, integration smoke, agent-doc lint, and evals when those tools exist. Load one primary skill from .cursor/skills/<name>/SKILL.md when it matches the task. Chain only when the primary skill says to.

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the single gate before calling work done:

    line 14
  2. Distinctive:

    No Riverpod, GetX, GetIt, Bloc, or client AI SDKs without user approval and a dated ADR.

    line 28
  3. Distinctive:

    Do not edit unrelated files or revert user changes.

    line 53
  4. Distinctive:

    Ask before adding new rules or skills.

    line 54
  5. Very specific:

    After touching code, update tests required by .cursor/rules/testing.mdc.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md

Agent-native Flutter starter. Keep changes minimal, verified, and aligned with the repository contract.

First Read

  1. docs/ARCHITECTURE.md for stack, folders, and boundaries.
  2. docs/CONVENTIONS.md for style, commits, and context rules.
  3. docs/DECISIONS.md before changing architecture or dependencies.
  4. Relevant context/ files before domain or project-specific work.

Verify

Run the single gate before calling work done:

dart run tool/verify.dart

This runs format, analyze, build_runner, tests with coverage, coverage threshold, integration smoke, agent-doc lint, and evals when those tools exist.

Stack Rules

  • Flutter stable, Dart 3.x, feature-first MVVM.
  • State and DI: provider + ChangeNotifier ViewModels.
  • Routing: go_router.
  • Models/errors: freezed + json_serializable; repositories return Future<Result<T, Failure>>.
  • No Riverpod, GetX, GetIt, Bloc, or client AI SDKs without user approval and a dated ADR.

Load Guides On Demand

  • docs/agent-guides/stack.md for MVVM, provider, routing, and data boundaries.
  • docs/agent-guides/testing.md for unit/widget/golden/integration expectations.
  • docs/agent-guides/security.md for secrets, logging, Supabase, and AI calls.
  • docs/BACKEND.md when enabling Supabase.
  • docs/QUALIFIED_AGENT_CONTRACT.md when changing rules, skills, or enforcement.

Skills

Load one primary skill from .cursor/skills/<name>/SKILL.md when it matches the task. Chain only when the primary skill says to.

  • plan-feature for non-trivial features or refactors.
  • flutter-implement for app code.
  • implement-tdd for red-green-refactor slices.
  • flutter-component for design-system components.
  • grind-until-green for analyze/test/build failures.
  • review-code for reviews.
  • doubt-review for auth, payments, migrations, deletion, or irreversible choices.
  • fix-dependencies, generate-mocks, write-commit, write-readme, save-context, monitor-terminal, suggest-rule, repo-navigator as needed.

Operating Norms

  • Do not edit unrelated files or revert user changes.
  • Ask before adding new rules or skills.
  • Save durable research in context/; save architecture decisions in docs/DECISIONS.md.
  • After touching code, update tests required by .cursor/rules/testing.mdc.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.