flutter_ui_layer

Rules for organizing the user-interface layer of a Flutter application. They separate screens and widgets from ViewModels, which hold screen state and coordinate data operations.

In plain words
What is it for?
Use them when building screens or ViewModels, wiring user interactions, managing screen state, and connecting views to repositories and asynchronous commands.
Why use it?
They keep screens simple and prevent display code from becoming mixed with business rules or data access.

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/moritzmessner/flutter-cursor-rules/flutter_ui_layer
Clone the repo
git clone --depth 1 https://github.com/MoritzMessner/flutter-cursor-rules

Made for: Cursor.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,092 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.00030 $0.01092
Opus 5 $0.00015 $0.00546
Sonnet 5 $0.00006 $0.00218
Haiku 4.5 $0.00003 $0.00109

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

Security

Grade A, and why

flutter_ui_layer 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 yesterday.

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/flutter_ui_layer.mdc · 192 lines

How it starts

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

🎯 UI Layer (Presentation)

Purpose: Display information and handle user interactions

Components:

  • Views (Widgets): Display UI, capture user input
  • ViewModels: Hold UI state, expose data and commands

Rules:

  1. Views MUST be as simple as possible
  2. Views MUST NOT contain business logic
  3. Views SHOULD be StatelessWidget when possible
  4. ViewModels MUST extend ChangeNotifier
  5. ViewModels MUST NOT import UI code
  6. ViewModels MUST use repositories for data operations
  7. All async operations MUST be wrapped in Commands (see flutter_design_patterns.mdc)

Example Screen

// ✅ CORRECT: Simple, delegates everything to ViewModel
class HomeScreen extends StatelessWidget {
  const HomeScreen({super.key, required this.viewModel});
  
  final HomeViewModel viewModel;
  
  @override
  Widget build(BuildContext context) {
    return ChangeNotifierProvider.value(
      value: viewModel,
      child: const _HomeScreenContent(),
    );
  }
}

class _HomeScreenContent extends StatelessWidget {
  const _HomeScreenContent();
  
  @override
  Widget build(BuildContext context) {
    final viewModel = context.watch<HomeViewModel>();
    
    return Scaffold(
      body: ListenableBuilder(
        listenable: viewModel.loadData,
        builder: (context, child) {
          // Handle loading state
          if (viewModel.loadData.running) {
            return const Center(child: CircularProgressIndicator());
          }
          
          // Handle error state
          if (viewModel.loadData.error) {
            return ErrorIndicator(
              title: 'Failed to load data',
              onRetry: viewModel.loadData.execute,
            );
          }
          
          // Show data
          return child!;
        },
        child: ListView.builder(
          itemCount: viewModel.items.length,
          itemBuilder: (context, index) {
            return ItemTile(item: viewModel.items[index]);
          },
        ),
      ),
    );
  }
}

Read the full file on GitHub · 192 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. yesterday First seen · 192 lines · 30 tokens per session scan A fe1cc078c5bd

Subscribe to this mod's changes

flutter_ui_layer is a cursor rule published in the GitHub repository MoritzMessner/flutter-cursor-rules (4 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 1,092 once invoked, about $0.0002 per session on Opus 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.