flutter-ai-starter / rules
Cursor rule0 starsChanged 5 months agoMITView on GitHub
Flutter widget performance, composition, and UI conventions
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/accessibility.mdcCursor rule
- .cursor/rules/api-integration.mdcCursor rule
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/dart-style.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/state-management.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- doubt-reviewSkill
- fix-dependenciesSkill
- flutter-componentSkill
- flutter-implementSkill
- generate-mocksSkill
- grind-until-greenSkill
- implement-tddSkill
- monitor-terminalSkill
- plan-featureSkill
- repo-navigatorSkill
- review-codeSkill
- save-contextSkill
- suggest-ruleSkill
- write-commitSkill
- write-readmeSkill
The file
We split this flutter-ui.mdc into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Keep widgets small; const constructors where possible
- Very specific: line 12
No business logic in build — observe ViewModels via context.watch / Selector / Consumer
- Distinctive: line 31
Test ViewModels in isolation without widget tree when possible
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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.
Files
--- description: Flutter widget performance, composition, and UI conventions globs: ["lib/**/*.dart", "test/**/*_test.dart"] alwaysApply: false --- # Flutter UI ## Widgets - Keep widgets small; `const` constructors where possible - No business logic in `build` — observe ViewModels via `context.watch` / `Selector` / `Consumer` - Stateless by default; `StatefulWidget` only for ephemeral local UI (focus, animations) - Min touch target ≥48dp (Material) / ≥44pt (Cupertino); add `Semantics` on interactive widgets ## Performance - ListView.builder for long lists; cache images appropriately - Dispose controllers and subscriptions in `StatefulWidget.dispose` - Narrow rebuilds with `Selector` or `Consumer` — avoid watching entire ViewModel when one field changes ## State - Shared/async app state lives in **ChangeNotifier ViewModels** via `provider` — not `setState` - Render loading/error/data explicitly from ViewModel fields or sealed UI state - Navigation and snackbars: triggered from ViewModel listeners or callbacks — not from `build` ## Testing - Widget tests with `ChangeNotifierProvider.value` overrides - Test ViewModels in isolation without widget tree when possible
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
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.