How codinginflow/nextjs-15-ai-resume-builder works
Main Components
• Frontend Interface: Represent the Next.js application’s UI, which is built using components under src/app (with clear route groups for authentication, billing, resume editor, etc.), components from src/components (including the premium UI and common UI components), and styling via Tailwind CSS and Shadcn UI.
• Authentication Module: Highlight (auth) routes under src/app/(auth) along with corresponding pages/sign-in and sign-up. This handles user login, registration, and session management.
• Resume Editor and Editor Flow: Separate out the editor interface (in src/app/(main)/editor) that handles multi-step forms, drag-and-drop, auto-save functionality, and dynamic form arrays.
• Billing and Subscription Module: Identify the billing sub-routes under src/app/(main)/billing, the relevant buttons/actions, and account subscription tier management, making it clear how the UI interacts with Stripe.
• API Layer and Webhook Integration: Mark the API endpoints under src/app/api (e.g., stripe-webhook) that are responsible for processing Stripe callbacks and possibly other server-side logic.
• Database and ORM Integration: Illustrate the database layer by referencing the prisma/schema.prisma, indicating that the app uses Prisma as its ORM for Postgres.
• External Services:
• Stripe: For handling payment and subscription workflow.
• ChatGPT API: For AI auto-fill capabilities in resume building.
• Vercel Blob: For file uploads.
Architectural Patterns and Design Principles
• Separation of Concerns: The app clearly separates authentication, billing, resume editing, and utility libraries to maintain modularity.
• Component-Based UI: With components spread across ui, hooks, and lib directories, the design promotes reusability.
• API-Driven Development: Using Next.js API routes to decouple the client from server operations.
• Integration with External Services: Stripe and ChatGPT integrations are modularized in the lib directory.