Design Firestore data models with collections, subcollections, denormalization strategies, and document references for optimal query performance. [EXPLICIT] Trigger: "firestore model", "firestore schema", "collection design", "denormalization"
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdtemplates/output.docx.mdtemplates/output.html"In NoSQL, you model for your queries — not for your data." — Unknown
Guides Firestore data modeling decisions — choosing between subcollections and root collections, when to denormalize, how to structure document references, and managing document size limits. Use when designing or refactoring Firestore database schemas for scalability and query efficiency. [EXPLICIT]
createdAt and updatedAt server timestamps to all documentsfirestore-queries — query patterns depend on data model designfirestore-security-rules — rules must align with document structureExample invocations:
| Scenario | Handling |
|---|---|
| Empty or minimal input | Request clarification before proceeding |
| Conflicting requirements | Flag conflicts explicitly, propose resolution |
| Out-of-scope request | Redirect to appropriate skill or escalate |
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.