mcpField
L
live-dev-storage-init

live-dev-storage-init

github.com/drgarbageCloud & DevOps055 installsUpdated 9w ago
Repository

About live-dev-storage-init

live-dev-storage-init is a skill for provisioning Firebase projects and Firestore resources. It guides configuration, security rules, deployment, and emulator-based local verification.

Key features

  1. 01Firebase project provisioning
  2. 02Firestore database setup
  3. 03Configuration file creation
  4. 04Firestore security rule authoring
  5. 05Emulator-based local verification

Use cases

  1. 01Setting up Firebase and Firestore for a backend
  2. 02Configuring Firestore before deployment
  3. 03Checking Firestore rules with the emulator

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/drgarbage/ag-course-index --skill live-dev-storage-init

After installing, type/live-dev-storage-initin Claude Code to confirm it loaded.

Bundled filesREADME.mdreferences/react-firestore-rules.md

Details

From the project README

live-dev-storage-init

This skill handles backend resource provisioning specifically for Firebase and Firestore database setup.

bash blocks are POSIX (Git Bash on Windows). Any logic beyond one command/pipe lives in resources/*.js (if applicable), never in shell control flow. If your Bash tool is cmd.exe or PowerShell, translate each snippet before running it.

1. Firebase & Firestore Provisioning

Configure or verify Firebase resources in this order:

ResourceSkip ifConstraints
Firebase project.firebasercProject ids are globally unique → generate <repo-name>-<rand4>, never ask the user to invent one.
Firestore databaseit already existsid is the literal '(default)' — quote it, bash eats the parens. Location us-central1 unless data-residency is stated.
firebase.jsonfile existsfirebase init firestore must run non-interactively; hand-write the file if it prompts. Without it, both deploy and the emulator fail.
firestore.rulesnever skipauthor before deploying: allow read, write: if false; + per-collection auth rules from references/react-firestore-rules.md. Deploy immediately — never leave test-mode rules live.
  • Blaze-plan features (Cloud Functions, outbound calls from triggers) need a card entered in the Console — the CLI cannot do it. This is the only legitimate console visit. On any billing/plan error: stop → name the single step → link https://console.firebase.google.com/project/<id>/usage/details → resume on confirmation.
  • Local QA verification using Firestore emulator should follow rules in references/react-firestore-rules.md.

Comments

Markdown supported