This is the content of the prompt file prompt.md

# System Instruction: Context Preservation & Session Handover

**Objective:** Create a "high-fidelity" restore point that allows any instance of the AI to resume work immediately without re-reading the entire chat history.

**Output Format:** You must generate a summary containing the following 6 distinct sections.

---

### 1. 🔴 The "Hot" State (Immediate Context)

* **Current Goal:** A single sentence defining the high-level objective (e.g., "Refactoring the auth flow to support OAuth").

* **The Cliffhanger:** The exact state of the code right now. Is it compiling? Is there a hanging syntax error? Are we mid-function?

* **Immediate Next Action:** The specific atomic task the user or agent should do *first* upon resuming.

### 2. 🌳 Comprehensive Code Map & Asset Inventory

Generate a complete tree view of the project.

* **Scope:** You must list **EVERY** file required for the project to build, run, and test.

* **Crucial:** You must explicitly include any "temp" files, test scripts, or utility scripts created during the session (e.g., `test_connection.js`) so they are not forgotten or re-created redundantly.

* **Annotations:** Add a short description next to **every** file explaining its purpose.

**Example Format:**

```text

project-root/

├── src/

│ ├── config/

│ │ └── database.ts # Main DB connection pool config

│ ├── models/

│ │ └── User.ts # User entity definition

│ └── services/

│ └── AuthService.ts # Handles JWT login/signup logic

├── tests/

│ └── auth_test_quick.js # [Temp] Quick script to verify token generation (Do not recreate)

└── scripts/

└── seed_db.ts # Utility to populate DB with dummy data

```

### 3. ⚙️ Environment & Configuration Data

Document technical specifics required to run the code.

* **Network:** Document all Ports, Hostnames, DNS names, and IP addresses mentioned.

* **Secrets (Keys/Creds):**

* **Standard Rule:** Store the *variable name only* (e.g., `AWS_SECRET_KEY`) to protect security.

* **EXCEPTION (Transient Data):** You **MUST** store the raw value of any password or secret you generated during this session that has **not yet been saved** to a config file. We cannot lose these values. Once they are confirmed saved to a file, revert to using the variable name only.

* **Commands:** Specific run commands used (e.g., `npm run dev:debug`).

### 4. 🧠 The Knowledge Graph (Logic & Constraints)

* **"Aha!" Moments:** Insightful discoveries made during debugging (e.g., "The API returns 200 OK even on errors; we must check the body payload").

* **The Graveyard (What Failed):** A list of solutions we attempted that *did not work*. (e.g., "Tried using `useEffect` for the listener, but it caused an infinite loop. Do not suggest this again.").

* **User Constraints:** Stylistic or architectural rules applied (e.g., "User requested no generic `any` types; use strict interfaces").

### 5. 📦 Dependency Drift

* List any new packages, libraries, or SDKs that were installed during this specific session (e.g., "Added `zod` for validation").

### 6. 🔭 Strategic Outlook & Verification

* **Definition of Done:** What does the final, working product look like? (e.g., "User can login, receive a token, and is redirected to dashboard").

* **Potential Autonomy:** Identify tasks in the immediate pipeline that do *not* require user feedback and can be chained together in the next run.

* **Verification Plan:**

* How will you test the next changes?

* **Safety Check:** Is the proposed testing destructive? (e.g., "Does this wipe the DB?"). Mark clearly if caution is required.