Frontend · Cursor
Flutter 3 & Riverpod / Dart .cursorignore
A .cursorignore for Flutter 3 & Riverpod / Dart that keeps build output, large files and secrets out of Cursor's index (best effort).
- Path
- .cursorignore
- Loads
- Indexing and AI features
- Format
- gitignore syntax
- Used by
- Cursor
What this file tells the agent
This .cursorignore keeps Flutter 3 & Riverpod / Dart build output, large data files and environment secrets out of Cursor's index and AI features, so context goes to your source code. It is best effort: commands the agent runs in the terminal can still read ignored files, so keep real secrets out of the repo too.
- Always add const constructors wherever possible to maximize Flutter element rebuild caching.
- Use Riverpod 3 with code generation (@riverpod, Notifier/AsyncNotifier) or BLoC; ban raw mutable setState() in business logic.
- Leverage Dart 3 pattern matching and sealed classes for exhaustive state and error representation.
- Enforce sound null safety: avoid force-unwrapping with ! unless proven non-null by a preceding guard clause.
- Separate presentation UI widgets from asynchronous repository and API service layers.
Code to avoid, and what to write instead
The rule steers the agent away from the left and toward the right.
// Discouraged: Mutable setState with force-unwrap and missing const
class BadProfile extends StatefulWidget {
@override
_BadProfileState createState() => _BadProfileState();
}
class _BadProfileState extends State<BadProfile> {
var user;
void load() async {
user = await fetchUser();
setState(() {});
}
@override
Widget build(BuildContext context) {
return Container(child: Text(user!.name)); // Runtime crash if null!
}
}import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';
@immutable
sealed class ViewState<T> {
const ViewState();
}
class Loading<T> extends ViewState<T> { const Loading(); }
class Success<T> extends ViewState<T> { final T data; const Success(this.data); }
class Failure<T> extends ViewState<T> { final String message; const Failure(this.message); }
class ProfileView extends ConsumerWidget {
const ProfileView({super.key});
@override
Widget build(BuildContext context, WidgetRef ref) {
final state = ref.watch(profileProvider);
return Scaffold(
appBar: AppBar(title: const Text('Profile')),
body: switch (state) {
Loading() => const Center(child: CircularProgressIndicator.adaptive()),
Success(:final data) => Center(child: Text('Welcome, ${data.name}')),
Failure(:final message) => Center(child: Text('Error: $message')),
},
);
}
}Install it in one command
- 01
Go to your project root
The file goes at .cursorignore, relative to the root.
- 02
Download the file
Run the command on the right. It downloads this preset and writes the file.
- 03
Make sure it gets used
Cursor applies .cursorignore automatically. Matching files leave the index and AI features, but commands the agent runs in the terminal can still read them.
$ curl -fsSL "https://www.devscratchpad.tech/api/raw/cursorignore/flutter-dart" -o ".cursorignore"
writes .cursorignore
.cursorignore
To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.
More for Flutter 3 & Riverpod / Dart
Questions
- How is .cursorignore different from .gitignore?
- .gitignore decides what git tracks. .cursorignore keeps files out of Cursor's codebase index and AI features; Cursor already skips files in .gitignore when it indexes.
- Does .cursorignore reduce wasted context?
- Yes. Ignored files are not indexed or pulled into requests, so build output and large data files do not crowd out your source code.