How teja-pola/gocart works
Project Type and Purpose
• goCart is a full-stack, embeddable AI shopping assistant—essentially a universal widget that any e-commerce site can drop in.
• It combines a React/Tailwind frontend, serverless functions (Netlify & Supabase Edge Functions), a PostgreSQL backend (Supabase), and integrations with external AI and data services (SerpAPI, Groq, ElevenLabs).
File Structure
• Top-level:
• src/ → Frontend React (Vite) code
• netlify/functions/ & src/server/ → Netlify serverless (Node/TypeScript)
• supabase/functions/ → Supabase Edge Functions (Deno/TypeScript)
• supabase/migrations/ & supabase/config.toml → Database schema and config
• .kiro/ → Internal docs and quality-gate hooks
• Public assets, config files (tsconfig, tailwind.config, netlify.toml)
• Patterns:
• Frontend vs. backend separation
• Serverless microservices
• Database migrations/versioning
• Zustand for client state management
• Proxy layer for SerpAPI (security and key-hiding)
Extract Architecture Insights from the README
• Frontend: TypeScript + React + Tailwind, delivered via Vite, deployed on Netlify CDN.
• Backend:
• Netlify Function at /.netlify/functions/serpapi-proxy for real-time Walmart data
• Supabase Edge Functions for cart agent logic & speech-to-text
• Supabase Auth and PostgreSQL DB for persistence
• AI Services:
• Groq API (Llama) for conversational AI
• ElevenLabs for voice synthesis
• SerpAPI for fetching product catalogs
Main Components & Their Interactions
a. Frontend Widget
• React component library (src/components)
• Zustand store (src/store) for cart/session state
• Styles with Tailwind
b. API Layer
• Netlify Function (serpapi-proxy)
• Supabase Edge Functions (cartify-agent, speech-to-text)
• Supabase Auth (JWT flows)
c. AI & External Services
• Groq API (user prompts → LLM)
• ElevenLabs (text → voice response)
• SerpAPI (product search)
d. Database & Persistence
• PostgreSQL via Supabase
• Migrations define tables, RLS policies
• Storage (if any media)
e. Hosting & CI
• Netlify (frontend + functions)
• Supabase (DB + Edge functions)
• .kiro hooks enforce linting, tests, security audits
Architectural Patterns & Design Principles
• Micro-frontends: single React widget that can be embedded anywhere
• Serverless microservices: each function has a single responsibility
• Event-driven state transitions (cart updates, API responses)
• Zero-trust API design: proxy functions prevent client-side secret leaks
• RLS (Row-Level Security) in Supabase for multi-tenant safety