How rithb898/fitforjob-ai-application-assistant works
Project type and purpose
• This is a full-stack web application (“FitForJob”) built with Next.js 15 (App Router) that helps job seekers generate AI-driven, personalized application materials (cover letters, LinkedIn messages, interview prep, etc.) by uploading a resume and entering job details.
• It combines a React-based front-end, serverless API routes, third-party services (Clerk, Groq AI, PostHog), PDF processing, and MongoDB persistence.
File structure
Top-level directories:
• app/ – Next.js App Router pages and API routes
– app/page.tsx, app/layout.tsx: Root layout and home page
– app/(auth)/…: Sign-in, sign-up via Clerk
– app/api/parse-resume, generate, regenerate: Serverless endpoints
– app/api/webhooks/clerk: Clerk authentication webhook
– app/create, history, response/[id]: UI pages for resume upload, history view, single response view
• components/ – Reusable UI components (forms, navbar, response section)
• lib/ – Business-logic modules: database setup (lib/db.ts), models, API actions, AI prompt builder (lib/prompt.ts), PostHog wrapper, storage utilities
• hooks/ – Custom React hooks for state, form submission, resume management
• public/ – Static assets
• middleware.ts – Next.js middleware, e.g., auth checks
• next.config.ts, tsconfig.json, eslint.config.mjs, postcss.config.mjs – Configuration
README insights
• Tech stack summary: Next.js + Turbopack, Tailwind CSS + Shadcn UI, React Hook Form + Zod, MongoDB, Clerk, PDF-parse, Groq AI (LLama 3.x), PostHog.
• Workflow overview: upload resume → /api/parse-resume → structure text → /api/generate → present responses → save/regenerate → persist in MongoDB & localStorage.
• Client (Browser/Mobile): React UI pages, form inputs, file upload, UI state hooks, Tailwind styles
• Frontend Layer: Next.js Server-Side Rendering (SSR) / Client-Side React components
• API Layer (Next.js serverless functions):
– /api/parse-resume
– /api/generate
– /api/regenerate
– /api/webhooks/clerk
• Business Logic (lib/actions, lib/prompt, hooks)
• Persistence: MongoDB cluster (user, resume, response collections), LocalStorage (for unauthenticated or caching)
• External Services:
– Clerk (Auth + webhooks)
– pdf-parse (resume text extraction)
– Groq AI SDK (LLama model inference)
– PostHog (analytics events)
• CDN / Vercel (Deployment platform)
1. Client → Next.js pages/components (UI rendering, form submission)
2. Client → /api/parse-resume (upload PDF) → pdf-parse → structured text → returns JSON
3. Client → /api/generate or regenerate → Groq AI → generated responses → returns JSON
4. API Layer → lib/db.ts → MongoDB (CRUD operations)
5. API Layer → lib/posthog → PostHog
6. Client + server → Clerk (authentication flows, webhooks)
7. Client → LocalStorage (cache resume, temporary responses)
c. Architectural patterns/design principles:
• Full-stack monorepo using Next.js App Router (co-located front/back)
• Serverless API functions for microservices-style endpoints
• Layered separation: UI, API, business logic, persistence, external services
• Unidirectional data flow in React + local/global state via hooks & stores (Zustand or custom lib/store)
• Validation at form layer (Zod) and at API boundary
– Next.js 15 (App Router, turbopack)
– React + Tailwind CSS + Shadcn UI
– React Hook Form + Zod
– pdf-parse, Groq AI SDK (LLama 3.x)
– MongoDB, Mongoose (models)
– Clerk (Auth)
– PostHog (Analytics)
Elements
• Labels: Component names (e.g., “ResumeUploader.tsx”, “/api/generate”)
• Blue rectangles for UI components
• Green rounded for API functions
• Purple clouds for external services
Detail
• API route as its own node.
• Internal libraries (lib/actions, lib/prompt) as sub-components.
• Don’t omit middleware.ts (e.g., auth guard).
• Both client storage (LocalStorage) and server storage (MongoDB).