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.
git clone --depth 1 https://github.com/MoritzMessner/flutter-cursor-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/moritzmessner/flutter-cursor-rules/flutter_design_patterns)<a href="https://agentmods.dev/rules/moritzmessner/flutter-cursor-rules/flutter_design_patterns"><img src="https://agentmods.dev/badge/rules/moritzmessner/flutter-cursor-rules/flutter_design_patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/moritzmessner/flutter-cursor-rules/flutter_design_patterns"><img src="https://agentmods.dev/badge/rules/moritzmessner/flutter-cursor-rules/flutter_design_patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00673 | $0.00673 |
| Opus 5.5 | $0.00269 | $0.00269 |
| Sonnet 5.5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
flutter_design_patterns 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎨 Design Patterns
1. Command Pattern
Purpose: Wrap async operations to handle loading, success, and error states automatically.
Use for: Async user actions, loading data, form submissions.
Implementation:
abstract class Command<T> extends ChangeNotifier {
Command();
bool _running = false;
bool get running => _running;
Result<T>? _result;
Result<T>? get result => _result;
bool get error => _result is Error;
bool get completed => _result is Ok;
void clearResult() { _result = null; notifyListeners(); }
}
class Command0<T> extends Command<T> {
Command0(this._action);
final Future<Result<T>> Function() _action;
Future<void> execute() async {
if (_running) return;
_running = true; _result = null; notifyListeners();
try { _result = await _action(); } finally { _running = false; notifyListeners(); }
}
}
class Command1<T, A> extends Command<T> {
Command1(this._action);
final Future<Result<T>> Function(A) _action;
Future<void> execute(A argument) async {
if (_running) return;
_running = true; _result = null; notifyListeners();
try { _result = await _action(argument); } finally { _running = false; notifyListeners(); }
}
}
2. Result Pattern
Purpose: Explicit error handling type.
Use for: Repository methods, potentially failing service methods.
Implementation:
sealed class Result<T> {
const Result();
factory Result.ok(T value) = Ok._;
factory Result.error(Exception error) = Error._;
}
final class Ok<T> extends Result<T> {
const Ok._(this.value);
final T value;
}
final class Error<T> extends Result<T> {
const Error._(this.error);
final Exception error;
}
3. Optimistic State Pattern
Purpose: Update UI immediately before server confirmation.
Use for: Likes, favorites, toggles.
Future<void> toggleFavorite(String id) async {
final wasFavorite = _favoriteIds.contains(id);
// Optimistically update
if (wasFavorite) _favoriteIds.remove(id); else _favoriteIds.add(id);
notifyListeners();
final result = await _repository.setFavorite(id, !wasFavorite);
// Rollback on failure
if (result is Error) {
if (wasFavorite) _favoriteIds.add(id); else _favoriteIds.remove(id);
notifyListeners();
// Show error...
}
}
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.
- 2mo ago First seen · 105 lines · 673 tokens per session scan A 06a61e09ead0
flutter_design_patterns is a cursor rule published in the GitHub repository MoritzMessner/flutter-cursor-rules (4 stars, last pushed 21d ago), licensed MIT. It adds 673 tokens to every session, about $0.0027 per session on Opus 5.5. 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-31.
Other cursor rules, from other repositories
swiftui-accessibility
SwiftUI accessibility rules for VoiceOver — labels, hints, traits, values, and attribute preservation.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.
figma-ios-codegen-workflow
Figma → iOS UIKit codegen workflow. Apply when the user mentions figma / figma.com and wants to convert or generate Swift/UIKit code. Enforces: data package first (preload CLI), bindings maps, full node coverage, audit.json, then coverage + screenshot verification. Do NOT load for unrelated tasks.
24-figma-assets
Figma MCP asset download preferences for Android XML — prefer SVG.
android-compose-accessibility
Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
flutter-taste
High-end Flutter UI design rules — anti-slop, bento grids, glassmorphism, parametric dials. Apply when writing or restyling Flutter widgets.