abidemia/nextjs-llm-orchestration-boilerplate

Purpose and Entry Points

This is a Next.js 14 App Router boilerplate for a multilingual LLM chat workflow, designed around lightweight UI delivery and an Edge-hosted API boundary. The browser enters through app/page.tsx, under the shared root shell in app/layout.tsx; chat requests are handled by app/api/chat/route.ts.

Application Shell and Client UI

app/layout.tsx establishes global document layout and imports shared styling from app/globals.css. app/page.tsx is the primary interactive screen and likely owns chat input, request initiation, and streamed-response presentation. Tailwind is the styling system, configured in tailwind.config.ts.

Chat API / Edge Execution Boundary

app/api/chat/route.ts is the server-side chat endpoint and the key trust/runtime boundary between browser requests and LLM orchestration. Per the repository design, this route is intended for Next.js Edge execution, minimizing latency by running close to callers rather than requiring a conventional long-lived Node server.

Typed Multilingual Prompt Contract

lib/types/index.ts centralizes TypeScript payload definitions used to make prompt orchestration deterministic across English, Pidgin, Hausa, Igbo, and Yoruba. The UI should submit a typed request shape to app/api/chat/route.ts; the route uses that structural contract to validate/select language-specific prompt behavior before producing its response.

Supabase Integration Boundary

lib/supabase/client.ts isolates Supabase client construction from application screens and route handlers. It depends on the public Supabase URL and anonymous key supplied through environment variables, providing a single place to change database/auth transport setup while keeping app/page.tsx and app/api/chat/route.ts independent of client initialization details.

Primary Request Flow

1. A user interacts with the chat UI in app/page.tsx.

2. The client assembles a typed multilingual chat payload from lib/types/index.ts.

3. The payload is sent to app/api/chat/route.ts.

4. The Edge route performs LLM/prompt orchestration and returns the response, potentially as a stream.

5. The UI consumes and renders the result; Supabase access, when needed, passes through the isolated client in lib/supabase/client.ts.

Runtime and Infrastructure

The material runtime is Next.js App Router with TypeScript, deployed in a serverless Edge-oriented model. Supabase provides PostgreSQL-backed cloud services through its JS client. Build output under .next/ is generated Next.js runtime and bundle material, not primary source architecture.