nrrajes/ai-recipe-generator

Purpose and Entry Points

This is an AI recipe generator structured as a Vite-served React/TypeScript client with an AWS Amplify backend. The browser application starts at src/main.tsx, renders its main UI from src/App.tsx, and is hosted through Vite’s HTML entry document at index.html.

Frontend Application Shell

The React UI is concentrated in src/App.tsx, with application-level styling in src/App.css and global styles in src/index.css. src/main.tsx is the client bootstrap boundary: it mounts React into the page and imports the app/style dependencies. There is no evidence in the tree of routing, multiple feature modules, or a separate API client layer.

Amplify Backend Composition

The backend is declared as Amplify infrastructure rather than a conventional server process. amplify/backend.ts is the composition entry point that assembles backend capabilities. Amplify’s own package and TypeScript setup are isolated under amplify/package.json and amplify/tsconfig.json, separating backend deployment definitions from the Vite client build.

Identity Boundary

Authentication is defined in amplify/auth/resource.ts. This is the backend identity boundary: frontend access to protected backend resources should be governed by the auth resource exported and composed through amplify/backend.ts. No client-side authentication integration files are present in src, so UI-level sign-in/session handling is either absent or embedded in the main app.

Data and AI Generation Stage

The data layer is defined in amplify/data/resource.ts. AI/Bedrock-specific behavior is isolated in amplify/data/bedrock.js, making it the likely integration boundary between application data operations and Amazon Bedrock recipe-generation calls. The expected control flow is: React user input → Amplify-backed data operation → Bedrock integration → generated recipe result returned to the UI.

Runtime and Deployment Boundaries

The client runs in the browser and is built/dev-served by Vite, configured in vite.config.ts; its root dependencies and scripts are in package.json. The backend targets AWS Amplify-managed infrastructure, with AWS authentication and Amazon Bedrock as material external services. The frontend/backend contract is represented by the Amplify data resource rather than an explicit REST server or standalone API process.

Current Architectural Maturity

The README is still primarily the stock React/Vite template and does not document application workflows, deployment, or model behavior. The repository’s meaningful domain architecture is therefore concentrated in the Amplify definitions—amplify/backend.ts, amplify/auth/resource.ts, amplify/data/resource.ts, and amplify/data/bedrock.js—while the client currently appears intentionally compact around src/App.tsx.