firestore-operations-manager

Manage Firebase/Firestore operations including CRUD, queries, batch processing, and index/rule guidance.Use when you need to create/update/query Firestore documents, run batch writes, troubleshoot missing indexes, or plan migrations.Trigger with phrases like "firestore operations", "create firestore document", "batch write", "missing index", or "fix firestore query".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️3downloads

When & Why to Use This Skill

The Firestore Operations Manager is a specialized Claude skill designed to streamline the management and optimization of Google Firebase/Firestore databases. It provides a robust framework for performing schema-aware CRUD operations, executing complex batch migrations, and troubleshooting performance bottlenecks like missing indexes. By integrating best practices for security rules and cost-efficiency, this skill empowers developers to maintain high-performance, scalable database architectures with ease.

Use Cases

  • Efficient Database CRUD: Seamlessly create, read, update, and delete Firestore documents with built-in schema awareness and validation.
  • Query Optimization & Indexing: Automatically identify required composite indexes for failing queries and generate the necessary configuration files to resolve performance issues.
  • Safe Data Migrations: Execute large-scale batch writes and field backfills across thousands of documents using checkpoints and rollback strategies to ensure data integrity.
  • Security & Access Control: Troubleshoot 'Permission Denied' errors by analyzing security rules and proposing least-privilege modifications to protect sensitive data.
  • Performance & Cost Monitoring: Detect query hotspots and propose sharding or pagination strategies to minimize latency and operational costs.
namefirestore-operations-manager
description|
allowed-toolsRead, Write, Edit, Grep, Glob, Bash(cmd:*)
version1.0.0
authorJeremy Longshore <jeremy@intentsolutions.io>
licenseMIT

Firestore Operations Manager

Operate Firestore safely in production: schema-aware CRUD, query/index tuning, batch processing, and guardrails for permissions and cost.

Overview

Use this skill to design Firestore data access patterns and implement changes with the right indexes, security rules, and operational checks (emulator tests, monitoring, and rollback plans).

Prerequisites

  • A Firebase project with Firestore enabled (or a local emulator setup)
  • A clear collection/document schema (or permission to propose one)
  • Credentials for the target environment (service account / ADC) and a plan for secrets

Instructions

  1. Identify the operation: create/update/delete/query/batch/migration.
  2. Confirm schema expectations and security rules constraints.
  3. Implement the change (or propose a patch) using safe patterns:
    • prefer batched writes/transactions where consistency matters
    • add pagination for large queries
  4. Check indexes:
    • detect required composite indexes and provide firestore.indexes.json updates
  5. Validate:
    • run emulator tests or a minimal smoke query
    • confirm cost/perf implications for the query pattern

Output

  • Code changes or snippets for the requested Firestore operation
  • Index recommendations (and config updates when needed)
  • A validation checklist (emulator commands and production smoke tests)

Error Handling

  • Permission denied: identify the rule/role blocking the operation and propose least-privilege changes.
  • Missing index: provide the exact composite index needed for the query.
  • Hotspot/latency issues: propose sharding, pagination, or query redesign.

Examples

Example: Fix a failing query

  • Request: “This query needs a composite index—what do I add?”
  • Result: the exact index definition and a safer query pattern if needed.

Example: Batch migration

  • Request: “Backfill a new field across 100k docs.”
  • Result: batched write strategy, checkpoints, and rollback guidance.

Resources