How rushyendra28/resace works
Project type and purpose
• From the file tree and README, we see:
• A Next.js 13 application (next.config.ts, src/app, page.tsx, layout.tsx)
• UI components under src/components/ui, styled with Tailwind (tailwind.config.ts, postcss.config.mjs)
• AI-driven “flows” under src/ai (ATS analysis, resume improvement, skill recommendations)
• A PDF parsing service under src/services/pdf-parser.ts
• It relies on Firebase for hosting/auth/data (not shown directly but alluded to as “firebase studio project”)
• Purpose: let users upload a resume (PDF), parse it, score / enrich it via AI flows, and match it to job descriptions.
File structure
• Top-level:
• src/app – Next.js route-based pages/server components
• src/components/ui – Design system primitives (buttons, dialogs, menus)
• src/ai – Business logic for AI-driven features (ai-instance.ts, flows/*.ts)
• src/services – Utility modules (PDF parser)
• src/lib – Generic utilities (utils.ts)
• src/hooks – React hooks for toast, mobile detection
• No self-hosted backend; it’s a front-end app that calls external services (AI provider, Firebase SDK).
README for additional insights
• A brief intro: “A firebase studio project… check resume score and job match… see src/app/page.tsx.”
Final checklist
• All components named and boxed separately
• Data flows shown with arrowheads and brief labels
• Critical config files (e.g., .env for Firebase keys) if relevant to deployment context