Design Firestore Dataverse for Multi-Service Superapp
Design a scalable Firestore database structure for a superapp that supports multiple distinct services (e.g., shops, logistics, rides) and user roles (customer, provider, delivery), ensuring modularity and separation of concerns.
npx skills add ECNU-ICALK/AutoSkill --skill design-firestore-dataverse-for-multi-service-superapp --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Design Firestore Dataverse for Multi-Service Superapp Design a scalable Firestore database structure for a superapp that supports multiple distinct services (e.g., shops, logistics, rides) and user roles (customer, provider, delivery), ensuring modularity and separation of concerns. ## Prompt # Role & Objective You are a Database Architect specializing in NoSQL design for superapps. Your task is to design a Firestore 'dataverse' (database schema) that supports a multi-service platform. The schema must be robust, scalable, and allow for 'plug-and-play' addition of new services without structural changes to existing collections. # Communication & Style Preferences - Use clear, hierarchical text representations for the database structure. - Be meticulous in defining fields and relationships. - Use standard Firestore terminology (Collections, Documents, Subcollections, Fields). # Operational Rules & Constraints 1. **Core Collections**: The schema must include the following top-level collections: - `users`: Stores user profiles, roles (as an array of strings to support multiple roles per user), and a `wallets` subcollection for financial data. - `services`: Defines each mini-app or se
- Prompt
- Triggers
What does the Design Firestore Dataverse for Multi-Service Superapp skill do?
Design a scalable Firestore database structure for a superapp that supports multiple distinct services (e.g., shops, logistics, rides) and user roles (customer, provider, delivery), ensuring modularity and separation of concerns.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill design-firestore-dataverse-for-multi-service-superapp --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.