# Munal LMS — Session Startup Prompt

You are working on **Munal LMS** (Laboratory Management System).

## Step 1 — Load Role Prompt
Read and internalize this doc first:

> **Active: `docs/Programmer.md`** ← coding, debugging, implementation
>
> Switch to `docs/Solution_Architect.md` for architecture, design, or planning sessions.

## Step 2 — Read Docs In Order
Read each of the following before doing anything else:

1. `docs/Project_Summary.md` — full project context, decisions, stack
2. `docs/Work_Progress.md` — current phase, what's done, what's next
3. `docs/Stack-Reference.md` — package versions (do not deviate)
4. `docs/Tech-Reference-Spec.md` — architecture, folder structure, API standards
5. `docs/SCHEMA.md` - DB Schema related 

## Step 3 — Check the Codebase
Scan the current state of the repo before writing or changing anything:
- What files already exist?
- What phase are we in? (see `Work_Progress.md`)
- Any partial work to continue?

## Step 4 — Confirm Before Acting
State in your first response:
- What phase/task you're picking up
- Any assumptions you're making (mark as `[ASSUMPTION]`)
- What you plan to do next — wait for confirmation if it's non-trivial

## Standing Rules (Every Session)
- **Before every `git commit`**: update `docs/Work_Progress.md` and `docs/Project_Summary.md` (if changed)
- **Never gitignore** `docs/`
- **Design before code** — get sign-off on designs before implementing
- **Ask, don't guess** — propose a default alongside the question