Cursor AI Rules for Flutter — Production-Ready .cursor/rules

Drop-in setup

.cursor/rules/*.mdc ships with every project — Cursor picks them up automatically.

Layer-scoped

Each rule file targets a layer (Data, Domain, Presentation) — the agent uses the right context.

Yours to extend

Plain .mdc Markdown — fork, override, layer your team conventions on top.

They trust us

Why you need AI coding rules

Without explicit rules, AI assistants default to generic Flutter patterns. With them, every suggestion follows your conventions — saving review time, preventing drift, and onboarding both humans and AIs from the same source of truth.

Stop fixing generic code

AI starts from your conventions, not Stack Overflow defaults. Less re-prompting, less rewriting.

Consistency across sessions

Every chat, every developer, every agent — same patterns. No more "which style won today?".

Onboard humans AND agents

New devs read the same file Cursor reads. One source of truth, zero docs duplication.

Survives team turnover

Your conventions are codified. They outlive any single contributor and scale with the team.

.cursor/rules folder with multiple .mdc files for Flutter projects

AI RULES

A curated set of rules, scoped per concern

Cursor reads every .mdc file in .cursor/rules/ on each prompt. ApparenceKit ships a curated collection — Flutter & Dart conventions, architecture, state management, design system, internationalization, testing. Each file declares its own glob pattern so the agent loads the right rules when editing the right code. No giant monolithic prompts, no missing context.

Flutter & Dart

Idiomatic Dart, null-safety patterns, Flutter widget conventions encoded

Per-layer scoping

Data-layer rules trigger on lib/data/**, presentation on lib/presentation/** — surgical context

Design system

Use the kit theme tokens for consistent styling and UI components

Internationalization

Generate ARB localizations alongside features by default

ARCHITECTURE

Aligned with the 3-layer pattern

The rules teach Cursor exactly where Data, Domain, and Presentation logic belong. Ask for a feature and the generated code lands in the right folder, uses the right repository pattern, and exposes a Riverpod notifier shaped like the rest of your codebase. Read more on the architecture template.

Layer boundaries

Cursor knows the Data layer talks to APIs, the Domain layer holds business logic, the Presentation layer reads state

Riverpod-first

Generated code uses Riverpod notifiers and providers — never setState spaghetti

Testable by default

Cursor scaffolds unit tests alongside features — mock repositories, override providers

Customize the .cursor/rules collection for your team

EXTEND

Customize without losing the baseline

The rules are a set of plain .mdc Markdown files you own. Add a new file, override an existing rule, scope to a subdirectory — each file is independent. ApparenceKit ships sane defaults so you don't start from a blank slate, but every rule is yours to amend.

One file per concern

Add a new .mdc rule without touching the others

Modular by default

Drop, swap, or fork any rule independently — no monolith to refactor

Team conventions

Layer naming, review, and shipping rules on top of defaults