Classes Management System - Architecture And Development Guide

Goal

Build a scalable MVP/prototype within 1 week for:

• Admin
• Teacher
• Student

This is not an ERP. The goal is a usable MVP with a scalable architecture, modular codebase, and AI IDE friendly structure.

Tech Stack

Frontend

• Next.js
• TypeScript
• Tailwind CSS
• shadcn/ui
• Redux Toolkit
• RTK Query
• React Hook Form
• Zod

Backend

• Next.js Route Handlers
• Prisma ORM
• PostgreSQL

Authentication

• Clerk

Storage

• Cloudinary
• Supabase Storage

Deployment

• Vercel
• Neon PostgreSQL or Supabase

Architecture

Frontend pages and components
  -> React Hook Form and Zod
  -> RTK Query
  -> Next.js API route handlers
  -> Feature service layer
  -> Prisma ORM
  -> PostgreSQL

Docs Index

• Folder structure
• API structure
• Routes
• Authentication
• Middleware and permissions
• Features and rules
• Database schema
• Development plan
• Frappe LMS reference
• Project progress

Main Rules

1. Use UUID everywhere.
2. Keep APIs modular.
3. Never hardcode role logic in components.
4. Use the service layer.
5. Use reusable tables and forms.
6. Keep feature-based architecture.
7. Store files externally.