hitansh911/smart-counseling-system

1. Overall shape

- This is a Next.js App Router application organized as a product site plus a logged-in workspace. The root app/ directory contains the public landing page, authentication routes, and the main authenticated application.

2. Public vs authenticated boundary

- app/(auth) holds sign-in and sign-up pages behind an auth-specific layout.

- app/(main) holds the application experience: dashboard, onboarding, resume builder, interview tools, and AI cover letters.

- middleware.js and lib/checkUser.js indicate route protection and session/user gating at the edge or request boundary.

3. Primary product domains

- The app is centered on job-search workflow features:

- dashboard for overview/status

- resume for building resumes

- interview for practice quizzes and performance tracking

- ai-cover-letter for generating and managing cover letters

- onboarding for initial user setup

- Each domain has its own route folder and local components, which keeps feature logic isolated.

4. Dashboard as the entry workspace

- app/(main)/dashboard contains a page and a dashboard-view component.

- This is likely the hub that aggregates user progress and links into the other product modules.

5. Resume workflow

- app/(main)/resume contains a resume-builder and entry-form.

- This suggests a structured form-driven creation flow where users enter resume data and the builder renders the final output.

6. Interview workflow

- app/(main)/interview is split into a mock interview page and reusable components such as quiz, quiz list, result view, stats cards, and a performance chart.

- The presence of both quiz UI and analytics components indicates a loop of practice, scoring, and performance history.

7. AI cover letter workflow

- app/(main)/ai-cover-letter includes a list page, a new/create page, a detail page by id, plus generator and preview components.

- This implies a CRUD-style content flow: create → list → inspect/edit/preview, with generated content stored and revisited later.

8. Onboarding as a required setup step

- app/(main)/onboarding contains a dedicated onboarding form.

- This likely captures user profile or job-search preferences that then influence dashboard content and generated artifacts like resumes or cover letters.

9. Shared UI and design system

- components/ui/ is a reusable component library built from common primitives such as buttons, dialogs, tabs, inputs, selects, progress, and toasts.

- components/header.jsx, components/hero.jsx, and components/theme-provider.jsx support the public marketing pages and global app shell.

- components.json suggests these UI primitives were scaffolded with a component system such as shadcn/ui.

10. Content and marketing layer

- The data/ directory contains static content collections like FAQs, features, how-it-works, industries, and testimonials.

- These files feed the homepage/marketing experience and keep presentation content separate from route logic.

11. Backend/data access layer

- lib/prisma.js and the prisma/ directory define the database layer.

- Prisma migrations show the app depends on a relational database with evolving models for users and industry-related data.

- app/lib/schema.js and app/lib/helper.js likely hold validation and shared server-side utility logic close to the App Router surface.

12. Background jobs and event processing

- lib/inngest/client.js, lib/inngest/functions.js, and app/api/inngest/route.js show an event-driven background processing path.

- This is the main asynchronous boundary in the system: the app emits events or jobs, and Inngest handles deferred processing through a Next.js API route.

13. State, fetching, and UX utilities

- hooks/use-fetch.js suggests a shared client-side data-fetching hook used by multiple features.

- components/ui/sonner.jsx indicates toast/notification handling for async actions like form submission, generation, or save flows.

- lib/utils.js likely contains formatting or class-name helpers shared across components.

14. Architectural summary

- The core architecture is: authenticated Next.js UI pages on top of a Prisma-backed database, with user access controlled by middleware/auth checks, and background work delegated to Inngest.

- The main product boundary is feature-based: dashboard, resume, interview, and AI cover letter are separate modules that share a common UI system, auth layer, and persistence layer.