flutterfire-configure
Skill669 starsChanged 3 months agoMITView on GitHub
Use when adding Firebase to a Flutter project, running flutterfire configure, initializing Firebase in main.dart, or configuring multiple flavors.
- Installs packages
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibilitySkill
- architecture-feature-firstSkill
- blocSkill
- code-reviewSkill
- dart-3-updatesSkill
- developing-genkit-dartSkill
- effective-dartSkill
- firebase-aiSkill
- firebase-analyticsSkill
- firebase-app-checkSkill
- firebase-authSkill
- firebase-cloud-firestoreSkill
- firebase-cloud-functionsSkill
- firebase-crashlyticsSkill
- firebase-databaseSkill
- firebase-data-connectSkill
- firebase-in-app-messagingSkill
- firebase-messagingSkill
- firebase-remote-configSkill
- firebase-storageSkill
- flutter-app-architectureSkill
- flutter-best-practicesSkill
- flutter-change-notifierSkill
- flutter-errorsSkill
- flutter-pre-cachingSkill
- flutter-use-column-row-firstSkill
- generate-images-with-firebase-aiSkill
- inclusive-designSkill
- mockitoSkill
- mocktailSkill
- patrol-e2e-testingSkill
- providerSkill
- revenuecat-testingSkill
- riverpodSkill
- testingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use this skill when:
- Very specific: line 69
Call WidgetsFlutterBinding.ensureInitialized() before Firebase initialization.
- Distinctive: line 70
Place Firebase initialization before any other Firebase service calls.
- Distinctive: line 79
After configuration, verify the setup is working:
- Very specific: line 81
Run flutter run and confirm the app launches without Firebase initialization errors.
- Very specific: line 82
Check the debug console for Firebase initialized successfully or similar confirmation.
- Very specific: line 83
Verify firebase_options.dart was generated with the correct project ID.
- Distinctive: line 86
Use a consistent Firebase project across all platforms for data consistency.
- Distinctive: line 88
Test the Firebase configuration with both debug and release builds.
- Distinctive: line 89
Check version compatibility between Flutter plugins and the underlying Firebase SDK.
- Distinctive: line 95
Create separate Firebase projects per environment (development, staging, production):
- Very specific: line 137
Use appFlavor or environment variables to select the configuration at runtime.
- Very specific: line 138
Import each flavor's config with namespace aliases (e.g., as dev).
- Distinctive: line 139
Use a helper script to automate multi-flavor configuration.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FlutterFire Configure Skill
This skill defines how to correctly set up and configure Firebase for Flutter applications.
When to Use
Use this skill when:
- Adding Firebase to a Flutter project for the first time.
- Running
flutterfire configureafter adding a new Firebase service or platform. - Initializing Firebase in
main.dart. - Setting up separate Firebase projects for multiple app flavors.
1. Prerequisites
Install the required tools:
npm install -g firebase-tools
firebase login
dart pub global activate flutterfire_cliMinimum platform requirements:
- Android: API level 19 (KitKat) or higher
- Apple: iOS 11 or higher
2. Setup and Configuration
# From your Flutter project directory:
flutterfire configure
# Add the core Firebase package:
flutter pub add firebase_core- Re-run
flutterfire configureany time you add support for a new platform or start using a new Firebase service. - For Android-specific services (Crashlytics, Performance Monitoring), the FlutterFire CLI automatically adds the required Gradle plugins.
- Rebuild with
flutter runafter adding new Firebase plugins.
3. Firebase Initialization
import 'package:firebase_core/firebase_core.dart';
import 'firebase_options.dart';
void main() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp(
options: DefaultFirebaseOptions.currentPlatform,
);
runApp(const MyApp());
}- Call
WidgetsFlutterBinding.ensureInitialized()before Firebase initialization. - Place Firebase initialization before any other Firebase service calls.
- Never modify
firebase_options.dartmanually — it is auto-generated. - Commit
firebase_options.dartto version control — it contains non-secret configuration identifiers. - For Firebase Emulator Suite:
await Firebase.initializeApp(demoProjectId: "demo-project-id").
4. Verification and Best Practices
After configuration, verify the setup is working:
- Run
flutter runand confirm the app launches without Firebase initialization errors. - Check the debug console for
Firebase initialized successfullyor similar confirmation. - Verify
firebase_options.dartwas generated with the correct project ID.
- Enable Firebase Analytics for optimal experience with Crashlytics, Remote Config, and other products.
- Use a consistent Firebase project across all platforms for data consistency.
- For iOS/macOS apps using certain Firebase services, add the Keychain Sharing capability in Xcode.
- Test the Firebase configuration with both debug and release builds.
- Check version compatibility between Flutter plugins and the underlying Firebase SDK.
5. Multiple App Flavors
Create separate Firebase projects per environment (development, staging, production):
flutterfire config \
--project=flutter-app-dev \
--out=lib/firebase_options_dev.dart \
--ios-bundle-id=com.example.flutterApp.dev \
--ios-out=ios/flavors/dev/GoogleService-Info.plist \
--android-package-name=com.example.flutter_app.dev \
--android-out=android/app/src/dev/google-services.jsonCentralize Firebase initialization by flavor:
// firebase.dart
import 'package:firebase_core/firebase_core.dart';
import 'package:flutter/services.dart';
import 'package:flutter_app/firebase_options_prod.dart' as prod;
import 'package:flutter_app/firebase_options_stg.dart' as stg;
import 'package:flutter_app/firebase_options_dev.dart' as dev;
Future<void> initializeFirebaseApp() async {
final firebaseOptions = switch (appFlavor) {
'prod' => prod.DefaultFirebaseOptions.currentPlatform,
'stg' => stg.DefaultFirebaseOptions.currentPlatform,
'dev' => dev.DefaultFirebaseOptions.currentPlatform,
_ => throw UnsupportedError('Invalid flavor: $appFlavor'),
};
await Firebase.initializeApp(options: firebaseOptions);
}// main.dart
void main() async {
WidgetsFlutterBinding.ensureInitialized();
await initializeFirebaseApp();
runApp(const MainApp());
}- Use
appFlavoror environment variables to select the configuration at runtime. - Import each flavor's config with namespace aliases (e.g.,
as dev). - Use a helper script to automate multi-flavor configuration.
References
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

