repository·main·Indexed 20 days ago
https://github.com/evanca/flutter-ai-rulesA collection of Flutter and Dart rules and 'skills' designed to enhance AI coding assistants such as Cursor, Windsurf, and Claude Code. It provides modular, documentation-based instructions and curated rule sets to ensure AI agents follow official best practices, including Effective Dart usage, Dart 3 patterns, Bloc architecture, and Mocktail testing.
Genkit Dart is an AI SDK for Dart providing a unified interface for AI agents, code generation, and structured outputs.
Core capabilities include:
Genkit()ai.generateai.defineToolai.defineFlowai.embedManyFor detailed API signatures and usage patterns, refer to the core framework reference at references/genkit.md.
Crashlytics collects reports automatically by default. You can control data collection to implement opt-in/opt-out flows.
It is best practice to disable collection during development to avoid polluting your production data:
if (kReleaseMode) {
await FirebaseCrashlytics.instance.setCrashlyticsCollectionEnabled(true);
} else {
await FirebaseCrashlytics.instance.setCrashlyticsCollectionEnabled(false);
}setCrashlyticsCollectionEnabled(true) to enable reporting (e.g., after a user grants permission).Records are anonymous, immutable, and strongly typed aggregate types used to bundle multiple objects. They are ideal for functions returning multiple values.
('first', a: 2, b: true).$1, $2, etc. Named fields are accessed by name (e.g., .a).var (name, age) = userInfo; or final (:name, :age) = userInfo; for named fields.// Creating a record
var userInfo = ('Alice', age: 30, isAdmin: true);
// Accessing fields
print(userInfo.$1); // Alice
print(userInfo.age); // 30
// Destructuring
var (name, age: userAge) = userInfo;
// Using type aliases for readability
typedef UserRecord = ({String name, int age});
UserRecord user = (name: 'Bob', age: 25);Riverpod provides several mechanisms to control when provider state is destroyed or cleaned up.
Disposal Strategies:
.autoDispose.keepAlive: true (codegen) or ref.keepAlive() (manual) to prevent automatic disposal.ref.invalidate(provider) to force destruction of state. If the provider is still being listened to, a new state will be created. Use ref.invalidateSelf() inside a provider to recreate itself.ref.onDispose to register cleanup code (e.g., closing a controller). Use ref.onCancel when the last listener is removed and ref.onResume when a new listener is added.Important: Always enable autoDispose for providers that receive parameters to prevent memory leaks from unused parameter combinations.
final myProvider = FutureProvider.autoDispose((ref) async {
final controller = SomeController();
// Register cleanup
ref.onDispose(() {
controller.dispose();
});
return controller.fetchData();
});To prevent tight coupling, features should never depend on each other's internals.
lib/common/ or in dedicated packages.enterprise-scale.md for patterns).Age-related decline often overlaps with established disability access needs. Instead of creating a separate "senior mode," implement standard accessibility practices to cover the four primary areas of age-related change:
Following WCAG (Web Content Accessibility Guidelines) is the standard way to address most of these needs.
Standardize your Bloc/Cubit implementation using these naming rules:
[BlocSubject][Optional Noun][Verb] (e.g., UserLoginPressed).[BlocSubject]Started (e.g., UserStarted).[BlocSubject] + Initial | Success | Failure | InProgress (e.g., UserSuccess).[BlocSubject]State with a Status enum (initial, success, failure, loading).Equatable, use @immutable, implement a copyWith method, and use const constructors.props getter when using Equatable to ensure correct equality checks.Campaigns are managed in the Firebase console under Messaging > In-App Messaging.
app_open, purchase_complete).Firebase Authentication provides different streams to observe changes in user state. Choose the stream that matches your requirements:
| Stream | Fires when |
|---|---|
authStateChanges() | User signs in or out |
idTokenChanges() | ID token changes (including custom claims) |
userChanges() | User data changes (e.g. profile updates) |
Example: Listening for sign-in/sign-out events
FirebaseAuth.instance
.authStateChanges()
.listen((User? user) {
if (user == null) {
print('User is currently signed out!');
} else {
print('User is signed in!');
}
});Note: Listen to these streams immediately upon app startup to handle the initial authentication state. Custom claims are only available after sign-in, re-authentication, token expiration, or manual token refresh.
Each component in the layered architecture has a specific role:
Follow these architectural principles to ensure maintainability:
View → ViewModel → Repository → Service. Lower layers must never import upper layers, and repositories should not depend on each other.BuildContext.blocs/, widgets/, or models/ folders that scatter feature code.initial, inProgress, failure, ready) to ensure exhaustive handling. Treat one-off effects (snackbars, navigation) as events rather than state.view-model → API client. Only introduce a Repository when caching, offline support, or merging sources is required. Only introduce a Use Case when logic is complex, reused by multiple view models, or merges multiple repositories.limit and offset in your GraphQL queries.@auth directive in your schema to enforce access levels (PUBLIC, USER, NO_ACCESS).