How baibhavbaidya/unspoken works
Project type & purpose (from file tree + README)
This is a full-stack Next.js (App Router) application. Even though the README is the default template, the file tree shows it’s not “just frontend”:
• UI + routing: app/** pages and layouts (App Router)
• Backend endpoints: app/api/**/route.ts (Next.js Route Handlers = server-side API)
• Authentication: app/auth/* pages, components/auth/ProtectedRoute.tsx, lib/auth-context.tsx, lib/firebase.ts
• LLM integration: lib/groq.ts, lib/prompts.ts, plus API routes like app/api/generate/route.ts and app/api/conversation/route.ts
• Domain concept: “bottles” and a multi-step “create” flow (app/bottles/**, app/create/**)
• client-rendered UI (React components)
• server-rendered routes
• serverless API endpoints
• external services (Firebase + Groq)
Reusable UI + client logic
• UI components: components/ui/* (navbar, hero, flowing-waves)
• Auth gating: components/auth/ProtectedRoute.tsx
• Hooks: hooks/use-mobile.tsx, hooks/use-toast.ts
• Types: types/index.ts
Server-side API surface (Backend inside Next.js)
• app/api/generate/route.ts
• app/api/conversation/route.ts
Shared “services” / integration layer (lib/*)
• lib/firebase.ts (Firebase client/admin initialization and config)
• lib/auth-context.tsx (auth state + context provider)
• lib/groq.ts (Groq API client / wrapper)
• lib/prompts.ts (prompt templates / prompt assembly)
• lib/utils.ts (shared utilities)
External dependencies / infrastructure
• Firebase (definitely Auth; possibly Firestore/Storage—confirm by checking lib/firebase.ts usage)
• Groq API (LLM generation / conversation)
Firebase Auth ↔ Browser/Next.js client (token-based session)
• Browser UI → Firebase Auth
• Browser UI → Next.js pages/components (obvious)
• ProtectedRoute/AuthContext → Firebase Auth SDK
Server calls Groq API
5. Response returns to UI to render results in /create/generate and subsequent steps (edit, deliver)
• Browser → Next.js API route (/api/generate, /api/conversation)
• API route → Groq API
• API route → prompt templates (internal dependency)
• API route → (optional) Firebase/DB if outputs are persisted (likely given “bottles”)
Bottles CRUD (domain data)
Pages suggest:
• /bottles
• detail: /bottles/[bottleId]
• create: /bottles/create
• Browser/pages → Firebase DB (or Next.js server → Firebase DB) depending on whether reads/writes happen client-side or via server routes.
• “End User (Browser)”
• “Next.js App (this repo)”
• “Firebase (Auth + DB)”
• “Groq API”
• User ↔ Next.js App
• Next.js App ↔ Firebase
• Next.js App ↔ Groq
Split “Next.js App” into:
• Web UI (App Router pages + components)
• API Routes (Route Handlers): /api/generate, /api/conversation
• Shared Libraries: lib/firebase, lib/groq, lib/prompts, lib/auth-context
External containers:
• Firebase Auth
• Firebase DB/Storage (if used)
• Groq API
• POST /api/generate → uses lib/prompts → uses lib/groq → calls Groq
• POST /api/conversation → conversation state handling (if any) → uses lib/groq
Shared helpers from lib/utils.ts and shared types/.
• Next.js App Router (app/)
• Route Handlers (app/api/*/route.ts)
• Firebase (Auth; DB if present)
• Groq (LLM inference)
• Styling/UI: Tailwind CSS (tailwind.config.ts, postcss.config.mjs, app/globals.css)
• Typescript everywhere (tsconfig.json, *.ts/tsx)
“Deployment” annotation:
• “Vercel Serverless Functions” (or “Node server runtime”) for API routes
Include:
• Clear labels: use route names and folder names (e.g., “/api/generate”, “Create flow pages: /create/interview|generate|edit|deliver”)
• Blue rectangles: Frontend UI (pages/components)
• Orange rectangles: Backend API routes