srikumar18/s3schools

Purpose and Entry Points

This is a split frontend/backend learning and interview-preparation application. The client is a Vite-style React SPA bootstrapped from frontend/src/main.jsx and composed through frontend/src/App.jsx. The backend is a Node application entered through backend/src/app.js, exposing authentication-oriented HTTP routes.

Backend API and Persistence

The backend separates application setup, database connection, routing, controllers, and models:

• Application/bootstrap: backend/src/app.js

• Database boundary: backend/src/config/database.js

• User persistence model: backend/src/models/user.js

• Authentication request handling: backend/src/controllers/authController.js

• Auth route registration: backend/src/routes/authRoutes.js

Requests flow from auth routes to the controller, which operates on the user model; database-specific details are isolated behind the database configuration module.

Authentication Boundary

Authentication is a dedicated cross-cutting backend concern. backend/src/middlewares/authMiddleware.js protects authenticated API paths, while backend/src/controllers/authController.js and backend/src/routes/authRoutes.js implement login/registration-facing endpoints. The frontend has corresponding account screens at frontend/src/pages/LoginPage.jsx and frontend/src/pages/RegistrationPage.jsx, with API communication centralized in frontend/src/services/api.js.

Study Plans and Problem Workflows

The client organizes learning-plan creation, plan consumption, topics, and coding problems as distinct UI flows:

• Plan creation and state orchestration: frontend/src/pages/CreatePlanPage.jsx, frontend/src/hooks/usePlan.js

• Plan and topic study views: frontend/src/pages/PlanPage.jsx, frontend/src/pages/TopicStudyPage.jsx

• Problem catalog and solving views: frontend/src/pages/ProblemsPage.jsx, frontend/src/pages/ProblemPage.jsx

• Supporting plan/problem presentation: frontend/src/components/PlanForm.jsx, frontend/src/components/CodeEditor.jsx, frontend/src/components/SubmissionResult.jsx

These flows are presently frontend-defined; the supplied tree only identifies backend routes for authentication.

AI Integration

AI functionality has explicit service boundaries on both sides:

• Backend generative-AI service: backend/src/services/genai.js

• Frontend Gemini-facing service: frontend/src/services/gemini.js

• Interactive assistant UI: frontend/src/components/AIAssistant.jsx

This separation suggests UI components should invoke service abstractions rather than embed provider calls directly. The generative-AI provider configuration and request shapes are not visible in the supplied tree.

Interview Session Subsystem

Interview functionality is a self-contained client subsystem with setup, active-session, and results stages:

• Page-level lifecycle: frontend/src/pages/InterviewSetup.jsx, frontend/src/pages/InterviewSession.jsx, frontend/src/pages/InterviewResults.jsx

• Interview state/control hook: frontend/src/hooks/useInterview.js

• Speech capture hook: frontend/src/hooks/useSpeechToText.js

• Session UI primitives: frontend/src/components/interview/QuestionDisplay.jsx, frontend/src/components/interview/AnswerInput.jsx, frontend/src/components/interview/InterviewTimer.jsx

The primary control flow is setup → timed question/answer session → results, with speech-to-text kept behind a dedicated browser-facing hook.

Runtime and Deployment Boundaries

The repository contains independently packaged frontend and backend runtimes: frontend/package.json and backend/package.json. The frontend includes frontend/vite.config.js, indicating a Vite build/development boundary; the backend owns server startup and database initialization via backend/src/app.js and backend/src/config/database.js. External dependencies materially implied by the structure are a database, a generative-AI service, and browser speech-recognition capabilities.