Agent skill · data analytics · aiskillstore
firebase-development-validate
This skill should be used when reviewing Firebase code against security model and best practices. Triggers on "review firebase", "check firebase", "validate", "audit firebase", "security review", "look at firebase code". Validates configuration, rules, architecture, and security.
Why this skill is useful
Adds a comprehensive checklist for validating Firebase code against security best practices and architecture patterns that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Firebase Code Validation Overview This sub-skill validates existing Firebase code against proven patterns and security best practices. It checks configuration, rules, architecture consistency, authentication, testing, and production readiness. Key principles: Validate against chosen architecture patterns Check security rules thoroughly Verify test coverage exists Review production readiness When This Sub-Skill Applies Conducting code review of Firebase project Auditing security implementation Preparing for production deployment User says: "review firebase", "validate", "audit firebase", "check firebase code" Do not use for: Initial setup → firebase-development:project-setup Adding features → firebase-development:add-feature Debugging active errors → firebase-development:debug TodoWrite Workflow Create checklist with these 9 steps: Step 1: Check firebase.json Structure Validate required sections: hosting - Array or object present functions - Source directory, runtime, predeploy hooks firestore - Rules and indexes files emulators - Local development config Check hosting pattern matches implementation (site:, target:, or single). Reference: docs/examples/multi-hosting-setup.md Step 2: Validate Emulator Configuration Critical settings: Verify all services in use have emulator entries. Reference: docs/examples/emulator-workflow.md Step 3: Review Firestore Rules Check for: Helper functions at top (isAuthenticated(), isOwner()) Consistent security model (server-write-only OR client-write-validated) diff().affectedKeys().hasOnly([...]) for client writes Collection group rules if using collectionGroup() queries Default deny rule at bottom Reference: docs/examples/firestore-rules-patterns.md Step 4: Validate Functions Architecture Identify pattern in use: Express: Check middleware/, tools/, CORS, health endpoint Domain-Grouped: Check exports, domain boundaries, shared/ Individual: Check one function per file structure Critical: Don't mix patterns. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/firebase-development-validate