ericrisco/rsc-harness / skills/firebase
firebase
VerifiedUse when building on Firebase — Firestore data modeling, Security Rules, Auth and custom claims, Cloud Functions, Storage, modular Web/Admin SDK imports — including symptoms like a database open to the internet, a query rejected by rules, or a doc stuck at ~1 write/sec. NOT managed-Postgres BaaS with SQL and RLS (that is supabase).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| evals/README.md | markdown | 944 B |
| evals/cases.yaml | config | 4.2 KB |
| references/cloud-functions.md | markdown | 3.9 KB |
| references/data-modeling.md | markdown | 3.9 KB |
| references/security-rules.md | markdown | 4.8 KB |
| scripts/verify.shexecutable | script | 4.2 KB |
evals/cases.yaml
View on GitHubskill: firebase
should_trigger:
- prompt: "Design the Firestore collections for a chat app with users, rooms, and messages. How should I structure it?"
why: "Core Firestore data modeling — collections vs subcollections, where messages live, denormalizing author info onto messages."
- prompt: "Can you review my firestore.rules? I'm worried the database is basically open to the internet."
why: "Rules audit and the headline 'open to the internet' risk — the catch-all open-rule failure mode the skill is built to catch."
- prompt: "My Firestore query works fine in the emulator but fails in production with a 'the query requires an index' error. What's going on?"
why: "Non-obvious: the emulator does NOT enforce composite indexes, so it silently runs queries that need an index declared in firestore.indexes.json."
- prompt: "Write a callable Cloud Function that sets a custom admin claim on a user after checking the caller is already an admin."
why: "Cloud Functions (2nd gen onCall) plus Auth custom claims set via the Admin SDK — squarely in scope and combines two product areas."
- prompt: "Necesito unes regles de seguretat perquè cada usuari només pugui llegir i editar els seus propis documents a Firestore."
why: "Catalan-language ownership Security Rules request — request.auth.uid == resource.data.ownerId; tests non-English trigger phrasing."
- prompt: "Our 'likes' counter document keeps choking under load and rejecting writes. How do I get past the 1-write-per-second limit?"
why: "Non-obvious scaling: the ~1 sustained write/sec/document soft limit and the sharded-counter remedy."
- prompt: "Should this be a subcollection under the room, or a separate top-level collection? I need to query messages across all rooms sometimes."
why: "Subcollection-vs-root decision driven by a collection-group access pattern — a named decision-table case."
should_not_trigger:
- prompt: "Design a normalized Postgres schema with foreign keys for orders and line items, and pick the right indexes."
route_to: postgresdb
why: "Relational SQL schema design with FKs and SQL indexing — engine-level Postgres, not a NoSQL document store."
- prompt: "Set up Supabase row-level security policies and wire up the postgres-js client for my app."
route_to: supabase
why: "Postgres-backed BaaS with SQL RLS and PostgREST — the closest sibling but a different data model and rules language (the NOT-boundary)."
- prompt: "Model a single-table DynamoDB design with a GSI to support my access patterns and capacity planning."
route_to: dynamodb
why: "AWS NoSQL with its own single-table/GSI and capacity model — different product entirely."
- prompt: "Configure GCP IAM roles and a billing budget alert for our Google Cloud project."
route_to: gcp-essentials
why: "Generic GCP IAM/billing, not a Firebase product surface — Firebase sits on top of GCP but this is the layer below."
- prompt: "Build the React component tree and state management for the analytics dashboard."
route_to: react
why: "UI component architecture that merely happens to call Firebase — a rendering/state concern, not data modeling or rules."
capability:
- scenario: "Here is a firestore.rules file with `match /{document=**} { allow read, write: if true; }` at the root, plus a `posts` collection where each post has an `ownerId` and users should only be able to read and edit their own posts. Fix the rules and explain how to test them locally."
must_include:
- "Removes the open `allow read, write: if true;` catch-all and relies on default-deny"
- "Ownership check: `request.auth.uid == resource.data.ownerId` for get/update/delete"
- "Uses `request.resource.data.ownerId == request.auth.uid` (or hasOnly/validation) on create"
- "Distinguishes the granular methods get / list / create / update rather than blanket read/write"
- "States that rules are NOT filters — the list query must be constrained (where ownerId == uid) or it is rejected entirely"
- "Provides a @firebase/rules-unit-testing snippet run via `firebase emulators:exec`"
- "Mentions App Check as the production trust boundary before rules evaluate"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |