How brulestl/tech-flow works
File structure
• Top-level: Dockerfile + dockerignore, env.local, package.json, Next.js config files, Tailwind & PostCSS configs.
• cache/: HuggingFace model/tokenizer blobs.
• public/: static assets + manifest.
• src/app/: the Next.js app router—routes for auth (login/signup), collections, recents, search, profile, and the root layout/page.
• src/components/: reusable UI pieces—layout (Header, Sidebar, Navbar), feature panels (ClusterPanel, SearchResultsPanel, SaveModal, etc.), UI primitives (SaveButton, SearchBar).
• src/lib/: supabaseClient.ts (initializes Supabase), utils.ts.
• src/styles/: global CSS.
• tsconfig, eslint, prettier, stylelint: code quality and typings.
README for additional insights
• Browser → Next.js (page requests)
• Browser ↔ Supabase (RPC via supabaseClient)
• Next.js → Supabase (server-side queries, if any)
• Next.js/Browser → Tokenizer Cache (file reads)
Detail is key
• Be explicit about data flow for each feature: auth flow, collections CRUD, recents retrieval, search calls, save operations.
• Both the static-asset serving (public/) and dynamic data pathways.
• Document any environment variables (env.local) that connect Next.js to Supabase.