This MVP was autonomously generated by MVP Factory v11 using a free-tier AI API (NVIDIA / Kimi K2.5). Simple logic runs for real. Complex external dependencies are stubbed so the app always works.

# Option A: Supabase (Postgres, free tier)
npm install @supabase/supabase-js
# In each route: import { createClient } from '@supabase/supabase-js'
# Replace the mock array with: const { data } = await supabase.from('table').select()

# Option B: PlanetScale (MySQL, free tier)
npm install @planetscale/database

Look for // TODO: replace with DB comments in src/app/api/**/route.ts

// In any API route, replace the hardcoded AI string with:
const res = await fetch('https://integrate.api.nvidia.com/v1/chat/completions', {
  method: 'POST',
  headers: { 'Authorization': `Bearer ${process.env.NVIDIA_API_KEY}`,
             'Content-Type': 'application/json' },
  body: JSON.stringify({
    model: 'moonshotai/kimi-k2.5',
    messages: [{ role: 'user', content: yourPrompt }],
    max_tokens: 1024
  })
});
const { choices } = await res.json();
return NextResponse.json({ result: choices[0].message.content });

Add NVIDIA_API_KEY=your_key to .env.local

npm install next-auth
# 1. Create src/app/api/auth/[...nextauth]/route.ts with your provider
# 2. Replace localStorage.setItem("auth_token",...) in auth/page.tsx with signIn()
# 3. Replace localStorage.getItem("auth_token") in dashboard/page.tsx with useSession()

npm install resend
# Replace the { sent: true } mock in notification routes with:
# await resend.emails.send({ from: 'you@domain.com', to: email, subject, html })

npm install stripe @stripe/stripe-js
# Replace demo payment routes with real Stripe checkout sessions

All the UI is already wired up. Every form already calls the right API route. You only need to swap the stubbed returns for real implementations.

Couples with vastly different caloric needs (e.g., 1200 cal IBS-friendly vs 2800 cal unrestricted) face daily friction planning, shopping, and cooking meals without waste or resentment

• ❌ Buying separate groceries creates waste and fridge clutter
• ❌ Resentment builds when one partner eats 'diet food' while other eats 'normal food'
• ❌ Decision fatigue from planning two different meals every night
• ❌ Difficulty tracking IBS triggers while cooking shared base ingredients

Dual-profile smart matching algorithm that pairs recipes with overlapping base ingredients but different portion scaling and macro adjustments

Unified grocery list generator with ingredient consolidation logic (e.g., buying 1 chicken breast for partner A, 3 for partner B, cooked together)

Synchronized cooking timeline scheduler that coordinates prep times so both meals finish simultaneously despite different portion sizes

IBS trigger conflict detector that flags shared ingredients problematic for restricted diets and suggests safe alternatives

Leftover optimization engine that converts dinner components into next-day lunches calibrated to each partner's caloric target

Weekly compromise resolver suggesting 'bridge meals' that satisfy both profiles when schedules or preferences clash

Shared pantry tracker with consumption rates per person to prevent over-purchasing bulk items only one partner eats

A step-by-step breakdown of how each feature is built. Use this as your dev roadmap.

What it does: Dual-profile smart matching algorithm that pairs recipes with overlapping base ingredients but different portion scaling and macro adjustments

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/dual-profile-smart-matching-algorithm-that-pairs-recipes-with-overlapping-base-ingredients-but-different-portion-scaling-and-macro-adjustments (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

What it does: Unified grocery list generator with ingredient consolidation logic (e.g., buying 1 chicken breast for partner A, 3 for partner B, cooked together)

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/unified-grocery-list-generator-with-ingredient-consolidation-logic (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

What it does: Synchronized cooking timeline scheduler that coordinates prep times so both meals finish simultaneously despite different portion sizes

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/synchronized-cooking-timeline-scheduler-that-coordinates-prep-times-so-both-meals-finish-simultaneously-despite-different-portion-sizes (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

What it does: IBS trigger conflict detector that flags shared ingredients problematic for restricted diets and suggests safe alternatives

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/ibs-trigger-conflict-detector-that-flags-shared-ingredients-problematic-for-restricted-diets-and-suggests-safe-alternatives (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

What it does: Leftover optimization engine that converts dinner components into next-day lunches calibrated to each partner's caloric target

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/leftover-optimization-engine-that-converts-dinner-components-into-next-day-lunches-calibrated-to-each-partner-s-caloric-target (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

What it does: Weekly compromise resolver suggesting 'bridge meals' that satisfy both profiles when schedules or preferences clash

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/weekly-compromise-resolver-suggesting-bridge-meals-that-satisfy-both-profiles-when-schedules-or-preferences-clash (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

What it does: Shared pantry tracker with consumption rates per person to prevent over-purchasing bulk items only one partner eats

How to implement:

Potential enhancements:

• ⚡ Cache repeated lookups with unstable_cache or Redis
• 🔒 Add rate limiting to /api/shared-pantry-tracker-with-consumption-rates-per-person-to-prevent-over-purchasing-bulk-items-only-one-partner-eats (e.g. Upstash Ratelimit)
• 📱 Make the UI section responsive-first (mobile breakpoints)
• 📊 Log feature usage to analytics (Plausible / PostHog)
• 🧪 Add an integration test for the API route

User Request
      │
      ▼
  Next.js Edge ──► API Route ──► Business Logic ──► Data Store
      │                               │
  React UI ◄────────────────── Response / JSON
      │
  Real-time UI Update

MVP Factory Validation Report — 2026-03-01
═══════════════════════════════════════════════════════

✅ PASS  Market Demand             █████████░ 9/10
✅ PASS  Competition Gap           ████████░░ 8/10
✅ PASS  Technical Feasibility     ████████░░ 8/10
✅ PASS  Monetization Potential    ███████░░░ 7/10
✅ PASS  Audience Fit              ████████░░ 8/10

─────────────────────────────────────────────────────
         OVERALL SCORE  ████████░░ 8.1/10
         VERDICT        🟢 BUILD — Strong market opportunity
         TESTS PASSED   5/5
═══════════════════════════════════════════════════════

Why this works: Exceptional Reddit validation (1982 upvotes, 494 comments) proves acute demand for this specific use case. No existing meal planner treats couples as a unit while respecting divergent physiological needs. The dual-profile optimization creates a genuine moat against generic planners. Freemium model fits weekly usage pattern while allowing viral growth through partner invites.

Unique angle: 💡 Treats the couple as a cooking unit rather than two isolated users, algorithmically optimizing for shared prep time and ingredient overlap while maintaining strict dietary boundaries

Competitors analyzed: PlateJoy (single-profile personalized planning), Eat This Much (macro-focused, individual use only), Mealime (simple family planning without caloric divergence handling)

Next.js 14 App Router + TypeScript + TailwindCSS + Lucide-react

# Clone & install
git clone https://github.com/guyromb/splitplate.git
cd splitplate
npm install

# Start development
npm run dev
# → http://localhost:3000

# Build for production
npm run build
npm start

# Add your keys here
NEXT_PUBLIC_APP_NAME=SplitPlate

Contributions are welcome! Here's how:

1. Fork the repo
2. Create your branch: git checkout -b feature/amazing-feature
3. Commit: git commit -m 'Add amazing feature'
4. Push: git push origin feature/amazing-feature
5. Open a Pull Request

MIT License — see LICENSE for details.