How mrvineet-raj/vibe works
Project type and purpose
• This is a full-stack Next.js web application (v15.3.4) using shadcn UI components.
• It provides user authentication (sign-in/sign-up), project management, messaging, usage tracking, and billing/pricing pages.
• The stack includes: Next.js App Router (src/app), React UI (components & modules/ui), TRPC for type-safe RPC APIs, Inngest for background workflows, Prisma ORM with PostgreSQL, and pnpm monorepo tooling.
File structure
• Top-level “src/app” directory: defines all Next.js pages and API routes.
• src/app/api/trpc/[trpc]/route.ts → TRPC endpoint
• src/app/api/inngest/route.ts → Inngest webhook entry
• src/app/(home), /projects/[projectId], /sign-in, /sign-up, /pricing → UI routes
• “src/components” & “src/modules”: UI components, shared primitives, and feature-scoped UI under modules/home, modules/projects, modules/messages, modules/usage.
• “src/trpc”: client & server TRPC initialization and routers (_app.ts).
• “src/inngest”: client helper, functions, and utils for background jobs.
• “src/lib”: Prisma client (prisma.ts), usage tracking helpers, generic utils.
• “prisma/”: schema.prisma plus migration folders & SQL files.
• Config files: next.config.ts, tsconfig.json, eslint.config.mjs, postcss.config.mjs.
Extract additional insights from README
• Uses Dockerized PostgreSQL (docker run … postgres).
• Implies local/dev DB, Prisma migrations to evolve schema.
Main components
a. Frontend (Browser/Next.js App)
• Next.js App Router → React components in src/app pages
• UI library: shadcn/ui + custom components (components/, modules/*/ui/)
b. API Layer (Next.js Server Functions)
• TRPC API endpoint: app/api/trpc → invokes src/trpc/routers → server procedures
• Inngest webhook endpoint: app/api/inngest → triggers background workflows
c. Business Logic / Domain Services
• modules/projects/server/procedures.ts
• modules/messages/server/procedures.ts
• modules/usage/server/procedure.ts
• src/lib/usage.ts (analytics/tracking)
d. Data Layer
• Prisma client (src/lib/prisma.ts) → interfaces with PostgreSQL
• PostgreSQL database (containerized)
e. Background Processing
• Inngest functions (src/inngest/functions.ts) → scheduled or event-driven jobs
• Inngest client (src/inngest/client.ts)
f. External Services
• Dockerized PostgreSQL
• (Optional) any third-party auth provider or billing API if added
Relationships and data flow
• Browser → Next.js server (SSR/SSG & client-side rendering)
• Browser UI → TRPC client → /api/trpc → TRPC router → domain procedures → Prisma → PostgreSQL
• Browser UI triggers Inngest events via Inngest client → /api/inngest → Inngest runtime → Inngest functions → DB or email/external
• Prisma migrations evolve the database schema (prisma/migrations)
• Usage tracking: domain logic calls src/lib/usage.ts to log consumption
Architectural patterns & design principles
• Clear UI/Business/Data separation
• Type-safe end-to-end with TRPC + Prisma
• App Router & file-based routing in Next.js
• Feature folders under src/modules to isolate domains
• Background tasks decoupled via Inngest webhook pattern
• Monorepo package management with pnpm/workspace
Detailed component breakdown
• src/app (Pages & API routes)
• src/components & modules/*/ui (UI widgets)
• src/trpc (init, client, routers, server.tsx)
• src/inngest (client, functions)
• src/modules/*/server (procedures per domain)
• src/lib/prisma.ts & usage.ts
• prisma/schema.prisma & migration folder
• Dockerized PostgreSQL instance