bede/tfm_ainventory
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: comprehensive cleanup and restructuring of project documentation

Browse Source
This commit is contained in:
Daniel Bedeleanu
2026-04-26 12:34:12 +03:00
parent b41a2dcf74
commit 2b42ec0d4d
19 changed files with 258 additions and 582 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
GEMINI.md
View File

@@ -4,23 +4,22 @@ You are Gemini (Antigravity), operating on the TFM aInventory project.
**IMMEDIATE MANDATORY ACTION:**
Before taking any action or writing code, you MUST read the following Single Source of Truth files:
1. `AI_RULES.md` (Contains your operational constraints, Git rules, and UI fidelity laws).
2. `PROJECT_ARCHITECTURE.md` (Contains the tech stack, data models, and system logic).
3. `dev_docs/SESSION_STATE.md` (Contains the current handover status from the previous AI).
1. `AI_MANDATES.md` (Operational constraints, Git rules, Handover protocols).
2. `DESIGN_SYSTEM.md` (UI/UX standards, Colors, Typography).
3. `CODING_STANDARDS.md` (Engineering rules, Testing, Security).
4. `ARCHITECTURE.md` (System logic, Data models, Offline sync).
5. `dev_docs/SESSION_STATE.md` (Current handover status).
**STRICT COMMUNICATION RULE:**
Be concise! Do not explain a thousand details unless they are absolutely necessary.
Be concise! Focus on signal over noise.
Do not proceed with any task until you have analyzed these three files.
DO NOT, EVER, USE "uppercase" or "toUpper" in any UI/UX context, nowhere. This SHOULD NOT be used in UI/UX anywhere, no text should be displayed in CAPITAL LETTERS! But do not replace "toUpper" with "toLower" or "uppercase" with "lowercase" either, leave text in UI/UX as is.
---
## graphify
This project has a graphify knowledge graph at graphify-out/.
- Use `graphify query`, `graphify path`, or `graphify explain` for architectural insights.
- Run `graphify update .` after significant code changes.
Rules:
- Before answering architecture or codebase questions, read graphify-out/GRAPH_REPORT.md for god nodes and community structure
- If graphify-out/wiki/index.md exists, navigate it instead of reading raw files
- For cross-module "how does X relate to Y" questions, prefer `graphify query "<question>"`, `graphify path "<A>" "<B>"`, or `graphify explain "<concept>"` over grep — these traverse the graph's EXTRACTED + INFERRED edges instead of scanning files
- After modifying code files in this session, run `graphify update .` to keep the graph current (AST-only, no API cost)
---
**Status**: ACTIVE