How prakharverma057/resume-analyzer works
Project type and purpose
• From the README and file tree, PathoraCV is a front-end web application (built with React, React Router/Vite, and Tailwind CSS) that lets users upload a resume, preview it, and get AI-driven analysis/feedback.
• There is no separate backend code in the repository; all logic (PDF conversion, analysis hooks) lives in the client, which calls out to an external AI service.
File structure
• Top-level config & build files: package.json, vite.config.ts, tsconfig*.json, Dockerfile.
• app/ directory:
• components/ – all reusable UI pieces (Navbar, FileUploader, ResumeAnalyzer, ResumeCard, ScoreBadge, etc.)
• hooks/ – custom hooks (useFileUpload).
• lib/ – client-side utility & service modules (pdf2img, reportDownloader, resumeAnalysis, Puter wrapper).
• root.tsx & routes.ts – application entrypoint & route definitions.
• routes/ – page components (home, upload, resume).
• constants/ – shared configuration values.
README for additional insights
• Confirms: Next.js-style app folder was adapted to Vite/react-router.
• Tech stack: React, Tailwind CSS, Vite, TypeScript.
• Feature callouts: resume upload & preview, AI analysis feedback, responsive layout.
Main components & interactions
a. Components:
• User (Browser)
• Static Hosting/CDN (serves index.html, JS bundles, public assets)
• Client Application:
– UI Layer (React components)
– Routing Layer (react-router, routes.ts)
– State/Context Layer (PuterProvider)
– Service Layer (hooks + lib modules: pdf2img, resumeAnalysis, reportDownloader)
• External AI Service API (calls from resumeAnalysis via Puter module)
• Optional Storage/Analytics (e.g., Vercel/Netlify analytics or file usage metrics)
b. Relationships/Data Flows:
1. User opens browser → requests static assets from Hosting/CDN.
2. Browser loads JS bundle → React app initializes (root.tsx & PuterProvider).
3. User navigates pages via react-router → UI components render.
4. FileUploader component & useFileUpload hook handle resume file → pdf2img converts PDF to images.
5. ResumeAnalyzer invokes resumeAnalysis lib → sends text or image data to External AI API → receives structured feedback.
6. UI components (ScoreBadge, Summary, Details) render analysis side-by-side with the preview.
7. reportDownloader exports results for user download.
c. Architectural patterns/design principles:
• Client-side rendering (CSR) SPA with code splitting via Vite.
• Context/provider pattern (PuterProvider) for managing AI API configuration & auth.
• Hook-based service layer decouples UI from business logic.
• Utility libraries (in app/lib) isolate PDF conversion, API calls, downloading.
d. Key technologies/frameworks:
• React & React Router for UI & routing
• Vite for bundling
• TypeScript for type safety
• Tailwind CSS for styling
• Puter (custom) for AI API abstraction
• pdf2img for PDF→image conversion