Firestore Expense Schema Design

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/firestore-expense-schema-designThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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.

---
id: "c3e6ef42-b521-4933-9c43-cdff5edd5b30"
name: "Firestore Expense Schema Design"
description: "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."
version: "0.1.0"
tags:
  - "firestore"
  - "database"
  - "schema"
  - "expenses"
  - "android"
triggers:
  - "firestore expense schema"
  - "database schema for expenses"
  - "firestore monthly daily structure"
  - "design expense database"
---

# 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

Excerpt, first 1,818 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Firestore Expense Schema Design

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology