SECURITY_FIREBASE.md Security
Firebase Auth with custom claims for RBAC, Security Rules as default-deny enforcement, App Check attestation, Cloud Function input validation, service role key protection, Secret Manager integration, and Emulator Suite isolation.
When to use: Reference when writing Firestore or Storage Security Rules, configuring Firebase Auth providers, implementing Cloud Function authorization, or auditing project permissions and IAM roles.
SCALABILITY_FIREBASE.md Scalability
Stateless Cloud Functions with global-scope connection reuse, Firestore triggers for async work, Pub/Sub fan-out, Cloud Tasks for controlled processing, hotspot avoidance, distributed counters, RTDB for presence, and composite indexes.
When to use: Reference when designing Firestore data models for scale, choosing between synchronous triggers and async processing, implementing counters or aggregations, or planning for high write throughput.
MAINTAINABILITY_FIREBASE.md Maintainability
Shared Cloud Function utilities, reusable Security Rule functions, typed Firestore converters, Emulator-based integration tests, Security Rules coverage testing, structured logging with Cloud Logging, and SDK version discipline.
When to use: Reference when organizing Cloud Function code, writing Security Rules tests, setting up CI with the Firebase Emulator Suite, or evaluating Firebase Extensions vs. custom implementations.
UIUX_FIREBASE.md UI/UX
Firestore offline persistence for optimistic UI, pending write indicators with snapshot metadata, Realtime listeners for instant updates, Cloud Function progress tracking, Remote Config for theming and A/B testing, and Firebase Analytics for UX measurement.
When to use: Reference when implementing real-time features, designing offline-capable user flows, setting up A/B testing with Firebase, or using Analytics to measure and improve user experience.
AVAILABILITY_FIREBASE.md Availability
Multi-region Firestore, Cloud Function regional deployment, min instances for critical functions, automatic retries with idempotency, dead-letter queues, PITR backups, Hosting preview channels, and deploy-from-CI-only discipline.
When to use: Reference when planning Firebase infrastructure for production, configuring Cloud Function scaling, setting up backup and recovery procedures, or designing deployment pipelines with rollback capability.
ADAPTABILITY_FIREBASE.md Adaptability
Remote Config for externalized strings, Firestore as a localized content store, Cloud Function localization with template loading, locale-aware Algolia/Typesense search indexing, and pluralization with Intl.PluralRules in functions.
When to use: Reference when adding multi-language support to a Firebase app, storing localized content in Firestore, implementing locale-aware search, or generating localized notifications and emails from Cloud Functions.
CLEAN_CODE_FIREBASE.md Clean Code
Cloud Function naming conventions, Firestore path naming, typed Firestore data with TypeScript interfaces, single-purpose functions, no side effects in Security Rules, idempotent design for at-least-once delivery, and no flag parameters.
When to use: Reference during all Firebase code writing and review. Essential for naming Cloud Functions, structuring Firestore paths, and ensuring trigger functions handle duplicate delivery correctly.
ARCHITECTURAL_DESIGN_FIREBASE.md Architecture
Layered Cloud Function organization, event-driven architecture with trigger chains, Firestore data modeling (denormalization, subcollections, root collections), Security Rules architecture, and separation of admin and client functions.
When to use: Reference when structuring a new Firebase project, designing Firestore document schemas, organizing Cloud Functions by responsibility, or planning the event-driven flow between triggers.
SOURCE_STRUCTURE_FIREBASE.md Structure
Firebase monorepo layout, index.ts as table of contents, one function per file, Security Rules formatting, import organization, test mirroring, environment configuration files, and Security Rules modularity with build steps.
When to use: Reference when setting up a new Firebase project directory, organizing Cloud Function source files, establishing Security Rules file structure, or configuring environment-specific settings.
DOCUMENTATION_COMMENTS_FIREBASE.md Documentation
Commenting Security Rule intent, documenting denormalization decisions and trigger chains, rate limit context, avoiding redundant Firebase SDK comments, schema documentation, Cloud Function dependency maps, and operational runbooks.
When to use: Reference when writing Security Rules, documenting Firestore schema decisions, creating operational documentation for Firebase projects, or establishing comment standards for Cloud Function code.