Skip to content

ComeOnOliver/skillshub / skills/aiskillstore/marketplace/2389-research/firebase-development

firebase-development

Verified

This skill should be used when working with Firebase projects, including initializing projects, adding Cloud Functions or Firestore collections, debugging emulator issues, or reviewing Firebase code. Triggers on "firebase", "firestore", "cloud functions", "emulator", "firebase auth", "deploy to firebase", "firestore rules".

Firebase Development

Overview

This skill system guides Firebase development using proven patterns from production projects. It routes to specialized sub-skills based on detected intent.

Sub-skills:

  • firebase-development:project-setup - Initialize new Firebase projects
  • firebase-development:add-feature - Add functions/collections/endpoints
  • firebase-development:debug - Troubleshoot emulator and runtime issues
  • firebase-development:validate - Review Firebase code for security/patterns

When This Skill Applies

  • Starting new Firebase projects
  • Adding Cloud Functions or Firestore collections
  • Debugging emulator issues or rule violations
  • Reviewing Firebase code for security and patterns
  • Setting up multi-hosting configurations
  • Implementing authentication (API keys or Firebase Auth)

Routing Logic

Keywords by Sub-Skill

project-setup:

  • "new firebase project", "initialize firebase", "firebase init"
  • "set up firebase", "create firebase app", "start firebase project"

add-feature:

  • "add function", "create endpoint", "new tool", "add api"
  • "new collection", "add feature", "build", "implement"

debug:

  • "error", "not working", "debug", "emulator issue"
  • "rules failing", "permission denied", "troubleshoot", "deployment failed"

validate:

  • "review firebase", "check firebase", "validate", "audit firebase"
  • "look at firebase code", "security review"

Routing Process

  1. Analyze Request: Check for routing keywords
  2. Match Sub-Skill: Identify best match based on keyword density
  3. Announce: "I'm using the firebase-development:[sub-skill] skill to [action]"
  4. Route: Load and execute the sub-skill
  5. Fallback: If ambiguous, use AskUserQuestion with 4 options

Fallback Example

If intent is unclear, ask:

Question: "What Firebase task are you working on?"
Options:
  - "Project Setup" (Initialize new Firebase project)
  - "Add Feature" (Add functions, collections, endpoints)
  - "Debug Issue" (Troubleshoot errors or problems)
  - "Validate Code" (Review against patterns)

Reference Projects

Patterns are extracted from three production Firebase projects:

ProjectPathKey Patterns
oneonone/Users/dylanr/work/2389/oneononeExpress API, custom API keys, server-write-only
bot-socialmedia/Users/dylanr/work/2389/bot-socialmedia-serverDomain-grouped functions, Firebase Auth + roles
meme-rodeo/Users/dylanr/work/2389/meme-rodeoIndividual function files, entitlements

Pattern Summaries

Multi-Hosting Setup

Three options based on needs:

OptionWhen to UseKey Feature
site: basedMultiple independent URLsSimple, no build coordination
target: basedNeed predeploy hooksBuild scripts run automatically
Single + rewritesSmaller projectsAll under one domain

Details: See docs/examples/multi-hosting-setup.md

Authentication

PatternWhen to UseExample
Custom API keysMCP tools, server-to-serveroneonone
Firebase Auth + rolesUser-facing appsbot-socialmedia
HybridBoth patterns neededWeb UI + API access

Details: See docs/examples/api-key-authentication.md

Cloud Functions Architecture

PatternWhen to UseStructure
Express appAPI with middleware, routingapp.post('/mcp', handler)
Domain-groupedFeature-rich appsposts.ts, journal.ts
Individual filesMaximum modularityOne function per file

Details: See docs/examples/express-function-architecture.md

Security Model

ModelWhen to UseComplexity
Server-write-onlyLight-write apps, high securitySimple rules
Client-write + validationHigh-volume writes, real-timeComplex rules

Strongly prefer server-write-only for light-write applications.

Details: See docs/examples/firestore-rules-patterns.md

Emulator-First Development

Always develop locally with emulators:

firebase emulators:start
# Access UI at http://127.0.0.1:4000

Key settings in firebase.json:

  • singleProjectMode: true - Essential for emulators to work together
  • ui.enabled: true - Access debug UI

Details: See docs/examples/emulator-workflow.md

Modern Tooling Standards

All Firebase projects follow these standards:

ToolPurposeConfig File
TypeScriptType safetytsconfig.json
vitestTestingvitest.config.ts
biomeLinting + formattingbiome.json

ABOUTME Comment Pattern

Every TypeScript file starts with 2-line ABOUTME comment:

// ABOUTME: Brief description of what this file does
// ABOUTME: Second line with additional context

Testing Requirements

  • Unit tests: Test handlers/utilities in isolation
  • Integration tests: Test with emulators running
  • Both required for every feature

Common Gotchas

IssueSolution
Emulator ports in uselsof -i :5001, kill process
Admin SDK vs Client SDKAdmin bypasses rules, client respects rules
Cold start delaysFirst call takes 5-10s, normal
Data persistenceUse Ctrl+C (not kill) to export data
CORS in functionsapp.use(cors({ origin: true }))

Summary

This orchestrator routes to specialized sub-skills:

  1. Detects intent via keywords
  2. Routes to appropriate sub-skill
  3. Sub-skills use TodoWrite checklists
  4. All reference shared patterns in docs/examples/

Sub-Skills:

  • firebase-development:project-setup - Initialize new projects
  • firebase-development:add-feature - Add functions/collections
  • firebase-development:debug - Troubleshoot issues
  • firebase-development:validate - Review code
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall