agentsclimarketplace

Firestore expense schema design

Skill ECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/firestore-expense-schema-design

AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution

Install
npx -y skills add ECNU-ICALK/AutoSkill --skill firestore-expense-schema-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, as published. Nobody here has run it

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 expenses
  • firestore monthly daily structure
  • design expense database

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.