How nota0515/guardian works
Project type and purpose
• Guardian is a full-stack web application whose primary goal is to guide users through DSA problems by offering hints and step-by-step approaches (not full code solutions).
• The README confirms it is built with a React/Vite frontend, an Express/Node.js backend, and integrates with an external AI chat service (“geminiChat”).
File structure
• Top-level directories:
• backend – contains an Express app (controllers, routes, middleware, models, service, config, index.js).
• frontend – contains a Vite/React app (pages, components, assets, API wrappers, styling).
• Configuration/deployment files: vercel.json in both frontend and backend, indicating Vercel hosting; vite.config.js, tailwind.config.js; db.js for database connection.
• Architectural patterns:
• MVC-style organization on the backend (models, controllers, routes, middleware).
• Service layer (backend/service/geminiChat.js) for external-AI integration.
• Front-end componentization (React components under src/components, pages under src/pages).
README for additional insights
• Tech stack: React + Vite, Tailwind CSS, Axios on the frontend; Node.js Express backend; external AI hints provider.
• App relies on an API (this backend) and may also call an external AI service (Gemini).
Elements
• Labels: each component (“React App,” “Express API,” “MongoDB,” “Gemini AI Service,” “Browser”)
• From Browser to React App (UI events)
• From React App to Express API (Axios calls)
• From Express controllers to DB and to Gemini service
• From DB back to Express, then to React, then to Browser
• Another for server-side components
• A third for external services
• A fourth for persistent storage