Firebase Firestore
Firebase (Google)OfficialCreated by Google LLCDistributed by Firebase (Google)
- Skill
- Tool integration
- Data and AI
- Apache-2.0
- Low risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a comprehensive framework for interacting with Google Cloud Firestore. It guides users through the lifecycle of a Firestore database, including instance provisioning, edition selection (Standard vs. Enterprise), data modeling, index management, and SDK integration across multiple platforms like Web, Android, iOS, and Flutter. It emphasizes architectural best practices, such as mandatory reference reading for SDK usage and proper security rule deployment.
What it does
- Lists and inspects existing Firestore database instances.
- Provisions new Firestore databases with specific edition and location settings.
- Provides structured guidance for data modeling using documents, collections, and subcollections.
- Facilitates SDK integration by providing platform-specific setup and initialization patterns.
- Manages database indexes and security rule deployment workflows.
- Enforces mandatory architectural checks before application code implementation.
When to use it
- When setting up a new Cloud Firestore database for an application.
- When migrating existing data or configuring database indexes.
- When integrating Firestore SDKs into Web, Android, iOS, or Flutter projects.
- When defining or updating data models for a NoSQL document-oriented structure.
- When troubleshooting or verifying database instance editions and configurations.
Advantages
- Ensures consistent database provisioning and configuration across environments.
- Provides clear paths for both Standard and Enterprise edition workflows.
- Promotes secure development practices by mandating security rule management.
- Reduces errors by requiring verification of SDK versions and architectural patterns.
Usage examples
- “List all my current Firestore databases and their editions.”
- The agent will execute the list command and provide a summary of all database IDs and their respective editions.
- “I need to set up a new Firestore database in the us-central1 region.”
- The agent will guide you through creating an Enterprise edition database in the specified location.
- “How do I query across all subcollections with the same name?”
- The agent will explain the concept of collection group queries and provide the necessary syntax for your platform.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/firebase/firebase-firestore/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip firebase-firestore.zip -d .agents/skills
Documentation by Google LLC
Cloud Firestore Database and Operations
[!IMPORTANT] Security Rules Authoring (
firestore.rules) Whenever setting up a Firestore-backed app or creating/modifyingfirestore.rules, configure"firestore": { "rules": "firestore.rules" }infirebase.jsonand deployfirestore.rules(npx -y firebase-tools@latest deploy --only firestore:rules), even if server routes use the Admin SDK:
If subagent delegation AND the
firestore-rules-authorsubagent are available: delegate authoringfirestore.rulesto thefirestore-rules-authorsubagent rather than writingfirestore.rulesdirectly in the main agent.If subagent delegation is unavailable (e.g., subagents not enabled in the IDE) OR
firestore-rules-authoris not installed: read and follow thefirestore-rules-creationskill to writefirestore.rulesdirectly.
Before setting up dependencies, writing data models, or configuring security rules, you MUST always identify the Firestore instance edition.
1. Instance Selection and Edition Detection
Run the following command to list current Firestore databases:
npx -y firebase-tools@latest firestore:databases:listA. Instance Found
For each database found, inspect its edition and details:
npx -y firebase-tools@latest firestore:databases:get <database-id>Ask the user which database instance they wish to target or if they would prefer to create a new instance.
Once the target instance is established:
If the
editionisSTANDARD, follow the guides underreferences/standard/.If the
editionisENTERPRISEor native mode, follow the guides underreferences/enterprise/.
B. No Instance Found (or New Requested)
If no databases exist or the user requests a new one, default to provisioning an
Enterprise edition database and ask the user what location to use. Run
npx -y firebase-tools@latest firestore:locations to get the list of options.
Suggest colocating with other resources if applicable.
Once the location is determined, create the database:
npx -y firebase-tools@latest firestore:databases:create <database-id> --edition="enterprise" --location="<selected-location>"Proceed with using the guides under references/enterprise/.
2. Specialized Guides
Based on the identified or created instance edition, open and read the corresponding reference guides:
Standard Edition (references/standard/)
Provisioning: Read provisioning.md
Security Rules: See the
firestore-rules-creationskillSDK Usage: Read web_sdk_usage.md, android_sdk_usage.md, ios_setup.md, or flutter_setup.md
Indexes: Read indexes.md
Enterprise Edition / Native Mode (references/enterprise/)
Provisioning: Read provisioning.md
Data Model: Read data_model.md
Security Rules: See the
firestore-rules-creationskillSDK Usage:
[!CRITICAL] Mandatory Reference Reading Before writing or modifying any application code for Firestore Enterprise Edition, you MUST read at least one of the relevant reference documents below for the target platform/language to understand specific architectural requirements and pipeline initialization patterns.
Read web_sdk_usage.md, python_sdk_usage.md, android_sdk_usage.md, ios_setup.md, or flutter_setup.md
Indexes: Read indexes.md
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md4.9 KiB
- references/enterprise/android_sdk_usage.md9.7 KiB
- references/enterprise/data_model.md2.8 KiB
- references/enterprise/flutter_setup.md4.6 KiB
- references/enterprise/indexes.md3.9 KiB
- references/enterprise/ios_setup.md5.8 KiB
- references/enterprise/provisioning.md3.2 KiB
- references/enterprise/python_sdk_usage.md3.0 KiB
- references/enterprise/web_sdk_usage.md4.6 KiB
- references/standard/android_sdk_usage.md6.6 KiB
- references/standard/flutter_setup.md4.5 KiB
- references/standard/indexes.md3.4 KiB
- references/standard/ios_setup.md5.3 KiB
- references/standard/provisioning.md2.8 KiB
- references/standard/web_sdk_usage.md4.4 KiB
references/standard/android_sdk_usage.md
Cloud Firestore (Standard edition) - Android Setup Guide (Kotlin)
This guide describes the SDK setup and basic usage patterns for Cloud Firestore
(Standard edition) in an Android app using Kotlin DSL (build.gradle.kts) and
Kotlin code.
Prerequisites
IMPORTANT: Before specifically working with Cloud Firestore, make sure to use
the skill and reference firebase_basics/references/android_setup to ensure the
following is done.
The Firebase CLI is available and authenticated.
An Android project exists and is registered with a Firebase Project.
The Android project has a Firebase config file (
google-services.json) and the Google services Gradle plugin (google-services).
1. Provision Firestore
Follow the instructions in firebase_firestore/references/standard/provisioning
to do the following:
Provision a Firestore instance (Standard edition)
Create or append a
firebase.jsonfileCreate a
firestore.rulesfileCreate a
firestore.indexes.jsonfileDeploy database, rules, and indexes
Run Firestore locally for development and testing
2. Add dependencies to Gradle build files
[!IMPORTANT] [AGENT] RESOLVING THE SDK VERSION DETERMINISTICALLY Never guess or hardcode a memorized out-of-date SDK or plugin version. Before adding dependencies, you MUST query the latest available versions directly from the Google Maven Repository:
# Find the latest Firebase Android BoM version curl -s https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-bom/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2 # Find the latest firebase-firestore version curl -s https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-firestore/maven-metadata.xml | grep -oE '<latest>[^<]+' | cut -d'>' -f2If the dependency is already declared, fetch the exact resolved version currently active in the workspace's build graph:
./gradlew -q :app:dependencyInsight --dependency firebase-firestore --configuration releaseRuntimeClasspath
In the module (app-level) build.gradle.kts (usually
<project>/<app-module>/build.gradle.kts), add the dependency for Cloud
Firestore:
dependencies {
// [AGENT] Fetch the latest resolved version using the Gradle command above
implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
// Add the dependency for the Cloud Firestore library
// When using the BoM, don't specify versions in Firebase library dependencies
implementation("com.google.firebase:firebase-firestore")
}3. Initialize Firestore
In the Activity or Fragment, initialize the FirebaseFirestore instance:
import com.google.firebase.Firebase
import com.google.firebase.firestore.FirebaseFirestore
import com.google.firebase.firestore.firestore
class MainActivity : AppCompatActivity() {
private lateinit var db: FirebaseFirestore
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
db = Firebase.firestore
setContent {
MaterialTheme {
Text("Firestore initialized!")
}
}
}
}Jetpack Compose (Modern)
Initialize inside a ComponentActivity using setContent:
import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Text
import com.google.firebase.Firebase
import com.google.firebase.firestore.firestore
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
val db = Firebase.firestore
setContent {
MaterialTheme {
Text("Firestore initialized!")
}
}
}
}4. Work with data
After Firestore is initialized, you can work with data in the following ways.
Add data
Add a new document with a generated ID using add():
// Create a new user with a first and last name
val user = hashMapOf(
"first" to "Ada",
"last" to "Lovelace",
"born" to 1815
)
// Add a new document with a generated ID
db.collection("users")
.add(user)
.addOnSuccessListener { documentReference ->
Log.d(TAG, "DocumentSnapshot added with ID: ${documentReference.id}")
}
.addOnFailureListener { e ->
Log.w(TAG, "Error adding document", e)
}Or set a document with a specific ID using set():
val city = hashMapOf(
"name" to "Los Angeles",
"state" to "CA",
"country" to "USA"
)
db.collection("cities").document("LA")
.set(city)
.addOnSuccessListener { Log.d(TAG, "DocumentSnapshot successfully written!") }
.addOnFailureListener { e -> Log.w(TAG, "Error writing document", e) }Read data
Read a single document using get():
val docRef = db.collection("cities").document("SF")
docRef.get()
.addOnSuccessListener { document ->
if (document != null && document.exists()) {
Log.d(TAG, "DocumentSnapshot data: ${document.data}")
} else {
Log.d(TAG, "No such document")
}
}
.addOnFailureListener { exception ->
Log.d(TAG, "get failed with ", exception)
}Read multiple documents using a query:
db.collection("cities")
.whereEqualTo("capital", true)
.get()
.addOnSuccessListener { documents ->
for (document in documents) {
Log.d(TAG, "${document.id} => ${document.data}")
}
}
.addOnFailureListener { exception ->
Log.w(TAG, "Error getting documents: ", exception)
}Update data
Update some fields of a document using update() without overwriting the entire
document:
val washingtonRef = db.collection("cities").document("DC")
// Set the "isCapital" field to true
washingtonRef
.update("capital", true)
.addOnSuccessListener { Log.d(TAG, "DocumentSnapshot successfully updated!") }
.addOnFailureListener { e -> Log.w(TAG, "Error updating document", e) }Delete data
Delete a document using delete():
db.collection("cities").document("DC")
.delete()
.addOnSuccessListener { Log.d(TAG, "DocumentSnapshot successfully deleted!") }
.addOnFailureListener { e -> Log.w(TAG, "Error deleting document", e) }Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
The author says: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Google LLC
- Publisher
- Firebase (Google) (Official)
- Distributed by
- Firebase (Google)
- Source
- firebase/agent-skills · skills/firebase-firestore · commit b76be96
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google LLC or Firebase (Google).
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download firebase-firestore.zip