conventions

A set of project-wide coding rules and documentation references for a Flutter application.

In plain words
What is it for?
Use it when creating or changing Flutter code so the work matches the project’s structure and documented conventions.
Why use it?
It gives code-generating tools the project’s expected architecture, naming, testing, and implementation patterns to follow.

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/abhinav503/flutter-agentic/conventions
Clone the repo
git clone --depth 1 https://github.com/abhinav503/flutter-agentic

Made for: Cursor.

Per session 3,298 This file is loaded in full into every session.
When invoked 3,298 The same file — it is already loaded in full.
Security scan B 1 finding. 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.03298 $0.03298
Opus 5 $0.01649 $0.01649
Sonnet 5 $0.00660 $0.00660
Haiku 4.5 $0.00330 $0.00330

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

Security

Grade B, and why

conventions scanned grade B with 1 finding 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

**Skills live in two parallel trees — keep them in sync.** Both Claude Code (`.claude/skills/`) and Codex CLI (`.codex/skills/`) read per-skill `SKILL.md` folders, but in different formats: Claude skills are thin (body +
.cursor/rules/conventions.mdc · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Index

Read before writing or modifying any code:

  • docs/reference/architecture.md — core folder map, layer patterns, naming, DI, error flow, design system, testing
  • docs/explanation/end-goal.md — project vision and guiding principles

Read on demand:

  • docs/how-to/contributing.md — contributor workflow and git hooks
  • docs/how-to/add-feature-template.md — full folder tree, empty class skeletons, DI wiring, and forbidden-pattern checklist for scaffolding a new feature
  • docs/how-to/add-usecase.md — create a use case class and register it in injection_container.dart
  • docs/how-to/design-screen-state.md — business-logic naming for events and states, retry context rules, screen rendering pattern; use the jokes feature as the reference
  • docs/how-to/review-code.md — when asked to review, audit, or check generated code; run through the full checklist and report ✅/❌ per section
  • docs/how-to/change-app-id.md — when asked to change the application ID or bundle identifier; covers Android (build.gradle.kts + MainActivity.kt package path) and iOS (project.pbxproj), with Xcode manual steps and provisioning notes
  • docs/how-to/rename-app.md — when asked to rename the app; covers display name, package name, and all files that reference the old name
  • docs/how-to/connect-firebase.md — when connecting an app to Firebase; covers checking/installing the Firebase + FlutterFire CLIs, running flutterfire configure, per-app firebase_core, main.dart init, Android Gradle plugin, iOS deployment target (15.0+), and the Xcode GoogleService-Info.plist registration check
  • docs/tutorials/solid-principles.md — how SOLID principles are applied across all layers; useful when designing new classes or reviewing layer boundaries
  • docs/tutorials/design-patterns-and-concepts.md — design patterns used in this codebase (Singleton, Repository, DTO, Either, Sealed Classes, Strategy, and more)
  • docs/explanation/ai-agents.md — per-agent install and usage
  • Release workflow — see release.mdc in this rules folder

Read the full file on GitHub · 171 lines

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 · 171 lines · 3,298 tokens per session scan B b66f65b62931

Subscribe to this mod's changes

conventions is a cursor rule published in the GitHub repository abhinav503/flutter-agentic (10 stars, last pushed 9d ago), licensed MIT. It adds 3,298 tokens to every session, about $0.0165 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.