TIS_RMS/frontend/AGENTS.md

BACKEND WORKFLOW (F:\SumbrerongBato\tis_rms_server\backend)

1. Read/Analyze Task → Inspect backend directory.
2. Draft Code → Execute Quality Gate (Accept / Decline).
3. Post-Code Loop: Analyze Errors → Resolve → Re-verify until Errors == 0.
4. Terminal Exit: If build clean → Execute git push.

FRONTEND WORKFLOW (F:\SumbrerongBato\tis_rms_server\frontend)

1. Read/Analyze Task → Inspect frontend directory.
2. Draft Components/Logic → Execute Quality Gate (Accept / Decline).
3. Post-Code Loop: Analyze UI/Build Errors → Resolve → Re-verify until Errors == 0.
4. Terminal Exit: If build clean & lint passes → Execute git push.

---

⚡️ TOKEN COMPRESSION PROTOCOL

1. INPUT RESTRICTIONS (CONTEXT DRYING)

• Ignore system-level file-tree re-reads unless files change (Δ).
• Avoid parsing historical chat history beyond the immediate code break.
• Reference internal libraries by name only; do not request full source mappings.

2. OUTPUT SYSTEM CONSTRAINTS (ZERO BLOAT)

• NO natural language intros, greetings, or conversational transitions.
• NO explanations, rationales, or "why this works" breakdowns.
• NO summaries of work completed or code recap commentary.
• Exclude all code comments, inline documentation, and docstrings.

3. PATCH FORMATTING (MICRO-DIFFS ONLY)

• BANNED: Full-file reprinting, multi-line blocks of unchanged code.
• MANDATORY: Return micro-diff format or target lines replacement only:

  - [old line]
  + [new line]
  

• If a file creation is required, generate minimal skeleton logic only.

4. QUOTA BRAKING

• Max output limit per prompt turn = 150 tokens.
• If patch logic requires >150 tokens: STOP, emit [TOKEN LIMIT BRAKE], and wait for chunked instructions.

---

📱 FLUTTER UI/UX RULES

• Stack: Flutter (latest) + Riverpod (AsyncNotifier/Notifier) + Material 3 (useMaterial3: true).
• Palette: Use existing Theme.of(context).colorScheme tokens only. Never hardcode hex values.
• Layout: Stack actions vertically on Android (Column with full-width ElevatedButton).
• Output: No design essays. Return optimized widget code immediately.

---

TODO

• dont do tasks with "(dont do)"

UI/UX RECOMMENDATIONS ROADMAP (TIS RMS UI-UX Recommendations.md)

Priority 1: Student Profile as Central Workspace

• Refactor student profile into primary operational hub: Overview, Documents checklist, and Activity History tabs.
• Direct inline document workflows (View, Upload, Verify, Print Queue) from student document tab.

Priority 2: Student Search & Filtering

• Transition student list to compact rows with direct status badges, LRN, and completion counters.
• Implement mobile bottom sheet for filtering (grade, section, status, school year) with active filter chips.

Priority 3: Status-Driven Documents & Requirements Workflow

• Integrate document requirements directly into Documents module workflow (All Documents, Requirements, Upload/Import, Print Queue).
• Add status system badges (✓ Complete, ⚠ Pending, ! Missing, ○ Archived) across document lists.

Priority 4: Action-Oriented Dashboard

• Add "Needs Attention" operational card (missing SF9/SF10, documents requiring verification).
• Add simplified recent operational activity feed linking directly to student targets.

Priority 5: OCR / Import Review Flow

• Implement 4-step wizard UI: Select Files → Processing → Review & Match Results → Confirm Commit.
• Allow manual student disambiguation on ambiguous or missing matches before database insertion.

Priority 6: Task-Specific Reports

• Refactor Reports into categorized tasks (Student Masterlists, Document Completion, School Forms SF9/SF10).
• Progressive filter modal (Report Type → Grade/Section → School Year → Format: PDF/Excel).

Priority 7: Human-Readable Activity History

• Reformat audit trail entries to plain English (User + Action + Target Student) with progressive disclosure for technical logs.

Priority 8: Navigation Drawer & Hierarchy

• Standardize drawer section labels: MAIN (Dashboard, Students, Documents, Archives) & ADMINISTRATION (Reports, Users, Activity History, Settings).

Priority 9: Feedback & State Standardization

• Implement skeleton loaders for list and folder views.
• Replace generic empty screens with actionable empty states (reason + clear CTA).
• Add lightweight persistent server connection status pill (Connected / Offline).

Priority 10: Adaptive Tablet / Desktop Navigation

• Implement adaptive Navigation Rail for tablet viewports and maintain persistent sidebar on desktop.

---

DONT DO

---

TIS_RMS Server Manager (dont do)

Windows Service - NSSM nodejs

• backup/restore db and files

• backup: database backup, automatic schedule, snapshot retention

• restore: restore database, validate backup, restart service automatically

• files: mirror backup, verify files, restore files,

• can choose where to store db and files separately

• dashboard: server status, cpu mem usage, connected users, uptime

• service: controls windows service stop start restart

• logs, server logs, error logs

• settings backup path, file backup path, database location

---