How kuroxi/thesis-vault works
Project type and purpose
• This is a full-stack Web application: a Library Management System built on Next.js (React) for the frontend and a TRPC/Prisma/Node backend.
• It follows Clean Architecture and Domain-Driven Design (DDD) to manage resources, users, roles, permissions, and audit logs with scalability in mind.
File structure
• Top-level folders:
• src/app – Next.js “app router” pages and layout (UI entry points).
• src/components – reusable React components (admin sidebar, data tables, forms, UI primitives).
• src/api (under src/app) – NextAuth “[…nextauth]” and TRPC route definitions.
• src/modules/user – core business module for user, role, permission, and audit-log DDD layers (domain, use cases, infrastructure, mappers, repositories).
• src/shared – common infrastructure for authentication, database connection, TRPC server/client setup, shared core (errors, result types).
• prisma – database schema.
• Config and infra:
• next.config.mjs, babel.config.json, postcss.config.mjs, tailwind.config.ts
• .env.example for environment variables, Supabase/Postgres connection, Google OAuth credentials.
• pnpm scripts for db:push and dev.
README for additional insights
• Confirms Clean Architecture & DDD.
• Describes tech stack: Next.js, pnpm, Supabase PostgreSQL, Google OAuth, Prisma migrations.