How whoisseth/ai-planner works
Project Type and Purpose
• It leverages modern architectural practices such as a tiered architecture, and uses technologies like Drizzle ORM, SQLite (or Turso), Arctic/Oslo for auth, and AWS SES for sending emails.
Analyzing the File Structure
• Notice several top-level configuration files (.env.sample, next.config.mjs, tailwind.config.ts, tsconfig.json) indicating the use of Next.js along with TypeScript and Tailwind CSS.
• The file tree splits the codebase into clear sections:
• “src/app” – Contains the Next.js App Router pages and grouped routes like “(auth)”, “(home)”, “dashboard”, etc.
• “src/api” – Includes API routes separated by concerns (chat, login, settings, etc.) which indicates clear back-end API endpoints.
• “src/db”, “migrations”, and “drizzle.config.ts” – Define the database schema and migration logic using Drizzle ORM.
• “src/data-access” and “src/use-cases” – Represent the business logic and data access layers.
• “src/lib” – Houses utility functions for authentication, emailing, session management, etc.
• “public” – Contains static assets like robots.txt, sitemap, sounds, etc.
• The presence of a “plan.md” and a “components.json” suggests documentation and possibly standardized UI components.