How amansingh0807/genform works
Project Type and Purpose
• Full-stack SaaS web application
• Purpose: AI-driven form generation, user subscriptions, analytics dashboard
File Structure
Top-level directories:
• app/ – Next.js 13 “app router” (UI pages, layouts, server actions, API routes)
• actions/ – Server-side form and user operations (Prisma + Stripe + AI)
• components/ & components/ui/ – React UI building blocks
• lib/ – Shared libraries (Prisma client, Stripe client, utilities)
• prisma/ – Database schema & migration scripts
• hooks/ – Custom React hooks (e.g. use-mobile)
• public/ – Static assets (e.g. screenshots)
• types/ – TypeScript type definitions
• middleware.ts – Next.js middleware (auth / routing guard)
Configuration files: next.config.ts, tsconfig.json, tailwind.config.ts
README
• Frontend: Next.js + React + Tailwind CSS
• Backend: Node.js via Next.js server actions + API routes, Prisma ORM
• External services: Stripe (subscriptions & payments), LLM (Gemini API)
• Hosting: Vercel / Render
Main Components & Their Interactions
A. Frontend (Next.js “app”):
– Layouts & pages under app/ for:
• Public routes (landing, sign-in, sign-up, success)
• Authenticated dashboard routes (forms management, analytics, upgrade)
• Form rendering (app/forms/[formId]/page.tsx)
– UI Components (components/ & components/ui/) used by pages
– React server components vs. client components (note files importing “use client”)
– Middleware handles auth checks on protected routes
B. Server Layer:
– Server Actions (actions/*.ts) invoked from React (form CRUD, submit, stats, subscription)
– Next.js API Routes (app/api/stripe/checkout-session/route.ts) for Stripe checkout sessions
– lib/prisma.ts exposes Prisma client to actions & API routes
– lib/stripe-client.ts + lib/stripe.ts encapsulate Stripe integration
– Gemini (AI) calls inside actions/generateForm.ts
C. Database:
– Prisma ORM maps to relational database (PostgreSQL) as defined in prisma/schema.prisma
– Migrations under prisma/migrations
– Models: User, Form, Submission, Subscription, etc.
D. External Services:
– Stripe API: payments, subscriptions
– Gemini (or another LLM) for AI form generation
– (Optional) Supabase – mentioned in README but not obvious in code
E. Hosting & Deployment:
– Vercel/Render hosting full stack via Next.js deployment
– Environment variables for DB_URL, STRIPE keys, AI keys
Architectural Patterns & Principles
• Server-side rendering + incremental static regeneration (Next.js)
• Server Actions for mutations (Next.js 13 feature)
• API Routes for third-party integrations
• Database abstraction via Prisma (repository pattern)
• Single codebase for frontend + backend (monorepo style)
• Component-based UI (atomic design in components/ui/)
• Middleware for cross-cutting concerns (authentication)