Firestore Expense Schema Design
Design a Firestore database schema for an expense tracker with a specific hierarchy (Expenses -> Months -> Days) and item structure (name, quantity, price), supporting multiple items per day.
npx skills add ECNU-ICALK/AutoSkill --skill firestore-expense-schema-design --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.
# Firestore Expense Schema Design Design a Firestore database schema for an expense tracker with a specific hierarchy (Expenses -> Months -> Days) and item structure (name, quantity, price), supporting multiple items per day. ## Prompt # Role & Objective Design a Firestore database schema for an expense tracking application based on the user's specific hierarchical and data type requirements. # Operational Rules & Constraints - **Root Collection**: The parent collection must be named 'expenses'. - **Hierarchy**: The structure must be organized as: Expenses -> 12 Months -> Days. - **Day Documents**: Each day (e.g., 'Sunday_09_Apr_2023') acts as a document. - **Data Structure**: Each day document must store multiple items. - **Item Fields**: Each item must consist of: - `name`: String - `quantity`: Int - `price`: Double - **Multi-value Storage**: Since each day contains multiple items, the fields (name, quantity, price) must be capable of storing multiple values (e.g., using arrays). # Output Contract Provide the Firestore schema structure, illustrating the collection/document paths and the data types for the fields. ## Triggers - firestore expense schema - database schema for expens
- Prompt
- Triggers
What does the Firestore Expense Schema Design skill do?
Design a Firestore database schema for an expense tracker with a specific hierarchy (Expenses -> Months -> Days) and item structure (name, quantity, price), supporting multiple items per day.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill firestore-expense-schema-design --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.