How kevin-pro123/agenda works
Project type and purpose
• This is a serverless full-stack “Agenda” application built with React (TypeScript) on the front end and Supabase (Postgres + Auth) on the back end.
• Its core features are CRUD for contacts and appointments, backed by Supabase tables and migrations.
File structure
• Top-level:
• src/ – React entry points (main.tsx, App.tsx), components, styling, types, and a Supabase client in src/lib/supabase.ts
• supabase/ – SQL migrations for contacts and appointments
• config files – vite.config.ts, tsconfig*.json, tailwind.config.js, postcss.config.js, eslint.config.js
• index.html, package.json, .env (user-provided)
• The src/components folder contains UI pieces (AppointmentForm/List, ContactForm/List, AuthModal) following a component-based UI pattern.
• No custom backend code—Supabase is used as an external service for database and auth.
README
• Confirms environment variables: VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY
• Standard install and dev commands: npm i, npm run dev
Final reminder
• Be exhaustive: capture all major pieces (UI, data library, services, config)
• Maintain readability: spacing, alignment, and consistent notation