feature-settings

A set of rules for settings screens in a Flutter application. It covers existing controls for haptic feedback, preventing sleep, themes, and boolean setting rows.

In plain words
What is it for?
Use it when building settings pages, adding boolean preferences, or wiring toggle rows to stored values. It also guides where settings files and components belong.
Why use it?
It helps developers reuse settings code instead of creating duplicate notifiers and widgets. It also identifies settings that are outside the package and need another solution.

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/sampaio-tech/flutter-core-modules/feature-settings
Clone the repo
git clone --depth 1 https://github.com/sampaio-tech/flutter-core-modules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,335 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.00000 $0.01335
Opus 5 $0.00000 $0.00668
Sonnet 5 $0.00000 $0.00267
Haiku 4.5 $0.00000 $0.00134

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

Security

Grade A, and why

feature-settings 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/feature-settings.mdc · 157 lines

How it starts

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

Feature: Settings — Rules

What Is Already Implemented — Check Before Building

Capability Status
Haptic feedback toggle (persisted) hapticFeedbackStateNotifierProvider
Prevent screen sleep / wakelock (persisted) wakelockStateNotifierProvider
Generic toggle row widget (not persisted) SwitchRowWidget
Toggle wired to any CacheBoolStateNotifier CacheBoolRowWidget
Dark / Light mode toggle row ThemeRowWidget
Auto-haptic on list row tap ✅ Built into LabelRowWidget.copyToClipboard / openLink
Notification permission settings ❌ Not in package — use app_settings package
Non-boolean persisted setting ❌ Not in package — implement following ThemeStateNotifier pattern

Before creating a new settings notifier or widget, verify whether the above already satisfies the requirement.


Layer Structure

lib/src/features/settings/
└── presentation/
    ├── notifiers/
    │   ├── haptic_feedback_state_notifier.dart
    │   └── wakelock_state_notifier.dart
    └── widgets/
        ├── switch_row_widget.dart
        ├── cache_bool_row_widget.dart
        └── theme_row_widget.dart

There is no domain or data layer — settings use the core CacheBoolStateNotifier directly.


Adding a New Boolean Setting

Extend CacheBoolStateNotifier with a unique key and default value:

class MyFeatureStateNotifier extends CacheBoolStateNotifier {
  MyFeatureStateNotifier({required super.getBoolUsecase, required super.setBoolUsecase, required super.removeCacheUsecase})
      : super(key: myFeatureKey(), defaultValue: true);
}

const _key = 'myFeature';
String myFeatureKey() => kDebugMode ? '${_key}Debug' : _key;

final myFeatureStateNotifierProvider =
    StateNotifierProvider<MyFeatureStateNotifier, bool>(
  (ref) => MyFeatureStateNotifier(
    getBoolUsecase: ref.read(getBoolUsecaseProvider),
    setBoolUsecase: ref.read(setBoolUsecaseProvider),
    removeCacheUsecase: ref.read(removeCacheUsecaseProvider),
  ),
);

Read the full file on GitHub · 157 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 · 157 lines · 0 tokens per session scan A fd977ad79b92

Subscribe to this mod's changes

feature-settings is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,335 tokens. 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.