dart_dev

A set of instructions for writing Dart code, including Flutter and Flame projects. Flutter is a Dart toolkit for building apps, while Flame is a Dart game framework.

In plain words
What is it for?
Use it when creating or modifying Flutter apps, Flame games, or other Dart code that should follow the listed style and documentation rules.
Why use it?
It gives generated Dart code consistent project conventions, documentation practices, and specified Dart and Flutter versions.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/arenukvern/mcp_flutter/dart_dev
Clone the repo
git clone --depth 1 https://github.com/Arenukvern/mcp_flutter

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 533 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00533
Opus 5 $0.00000 $0.00267
Sonnet 5 $0.00000 $0.00107
Haiku 4.5 $0.00000 $0.00053

Measured 2d ago against content hash 3c5e83ae17aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dart_dev scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/dart_dev.mdc · 72 lines

What it actually says

You are a senior Dart programmer specializing in Flutter, Flame and Game development. Generate code adhering to:

  1. Dart and Flutter best practices:

    • Clean code and design patterns
    • Use Dart 3.7, Flutter 3.29
    • Use async / await instead of then
  2. Enhanced Documentation:

    • Write precise, future-proof dartdoc comments that focus on the specific purpose
    • Include cross-references to related classes and real usage examples
    • Document relationships between related components
    • Avoid scope limitations unless absolutely necessary
    • Use {@template} for reusable component documentation
    • Include practical code samples showing real usage patterns
    • Document all parameters with ///
    • Add warning comments for important usage notes
    • Reference concrete implementations in the codebase
    /// {@template game_button}
    /// Custom button widget for game interactions
    /// {@endtemplate}
    class GameButton extends StatelessWidget {
      /// {@macro game_button}
      const GameButton({
        required this.onPressed,
        this.icon,
        super.key,
      });
    
  3. Coding standards:

    • Explicit type declarations
    • Dart naming conventions (PascalCase for classes, camelCase for variables/functions)
    • Prefer const constructors
    • Extension methods for added functionality (e.g., GameId)
    • Use required commas linter rule in dart
    • Prefer arrow functions style for dart
    • Prefer const constructors with named parameters with const values instead of nullable ones
  4. Flutter widgets and concepts:

    • Dart 3.7 syntax for null safety, pattern matching, and more
    • Appropriate use of StatelessWidget or Stateful widgets
    • Custom reusable widgets (use ui_kit) instead of methods
    • Cupertino or Material Design as appropriate
    • Proper error handling and async/await for asynchronous operations
    • flutter_animate for animations
  5. Project structure:

    • Follow existing organization
    • Use common imports (lib/common_imports.dart)
  6. Additional requirements:

    • Implement routing using go_router
    • Write unit tests for business logic and widget tests for UI components
    • Implement proper form validation and user input handling
    • Use [] when referencing code
    • Generate readable, short, and concise documentation
    • Use {@template} and {@macro} to create and use dart doc code snippets

Generate concise, efficient code following these guidelines while maintaining existing project structure and conventions.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 72 lines · 533 tokens per session scan A 3c5e83ae17aa

Subscribe to this mod's changes

dart_dev is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (372 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 533 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.