How dmdeepakmehta/spend works
Project type and purpose
• This is a full-stack web application: an AI-driven personal finance platform built with Next.js (App Router), Tailwind CSS, Prisma (PostgreSQL via Supabase), Inngest for background jobs, ArcJet for AI embedding, Clerk for authentication, Shadcn/UI for components, and Resend for emails.
• Users sign up/sign in, manage budgets, view dashboards, create transactions (with receipt scanning), and receive summary emails.
File structure
• Top-level config: next.config.mjs, postcss.config.mjs, tailwind.config.js, middleware.js, jsconfig.json, .eslintrc.json.
• “app” directory (Next.js App Router): authentication routes (app/(auth)), main UI (app/(main)), global layout (app/layout.js), API routes (app/api/inngest, app/api/seed).
• “actions” directory: Inngest cron / function definitions (account.js, budget.js, dashboard.js, seed.js, send-email.js, transaction.js).
• “lib” directories:
• app/lib/schema.js (Zod or GraphQL schemas)
• lib/arcjet.js (AI embeddings), lib/checkUser.js, lib/inngest/client.js, lib/inngest/function.js, lib/prisma.js, lib/utils.js
• “prisma” folder: database schema and migrations.
• “components” and “components/ui”: shared React UI and Shadcn offerings.
• “data”: seed or static data (categories, landing).
• “emails”: JSX templates for Resend.
README for additional insights
• The stack: Next.js, Supabase, Tailwind, Prisma, Inngest, ArcJet, Shadcn UI, Clerk, Resend.
• Environment variables drive database, authentication, AI API keys, email service.