The Best Google Antigravity Prompts for Building a SaaS MVP

Build a complete, production-ready SaaS MVP called [YOUR_PRODUCT_NAME].

## Product Overview
**What it does**: [BRIEF_DESCRIPTION]
**Core problem**: [MAIN_PAIN_POINT]
**Target users**: [WHO_USES_IT]
**Key features**: [LIST_2_4_CORE_FEATURES]

## Technical Requirements

**Tech Stack** (use exactly these):
- Next.js 15 (App Router)
- TypeScript (strict mode)
- Tailwind CSS + Shadcn UI components
- Supabase (PostgreSQL database)
- Drizzle ORM
- Kinde Auth (authentication)
- Stripe (payments)
- Resend (transactional emails)

**Database Schema Requirements**:
- Standard users table with: id (varchar 255), email, firstName, lastName, role, createdAt, stripeCustomerId, stripeSubscriptionId, subscriptionStatus, subscriptionEndsAt
- 2-4 custom tables for the product's core features
- Use snake_case for DB columns, camelCase for TypeScript
- Foreign keys to users.id (varchar 255)
- Proper indexes on frequently queried fields
- Generate SQL I can run in Supabase (don't use drizzle-kit push)

**Application Structure**:
- Server Actions in app/actions/ for all CRUD operations
- React components using shadcn UI (Dialog, Card, Button, Input, Textarea, Badge, Tabs)
- Main dashboard at app/dashboard/page.tsx with stats and data management
- Landing page with Framer Motion animations
- Custom theme (choose 2 Google Fonts + brand colors matching the product personality)

**Subscription Model**:
- Free plan: [DEFINE_LIMITS - e.g., 5 items max, basic features]
- Plus plan: $49/year with unlimited access
- Stripe checkout integration
- Webhook handlers for subscription lifecycle
- Plan enforcement in server actions

**Email Flows**:
- Welcome email when user signs up
- Subscription confirmation after checkout
- Use @react-email/components for templates

## Quality Standards

**Security**:
- Every server action must check authentication with getKindeServerSession
- Filter all database queries by userId
- Validate all user inputs
- Never expose secrets in client code
- Use environment variables for API keys

**UX/UI**:
- Mobile-first responsive design
- Professional look (like DoorDash or Stripe - not rushed)
- Loading states for all async operations
- Error handling with helpful messages
- Onboarding flow for new users
- Toast notifications for feedback

**Code Quality**:
- TypeScript strict mode
- Functional components with hooks
- "use client" only for interactive components
- Server components by default
- Call revalidatePath after mutations
- Proper error boundaries

## Deliverables

When complete, I should have:
1. ✅ Working application at localhost:3000
2. ✅ Database schema + SQL to run in Supabase
3. ✅ All core features functional (CRUD operations working)
4. ✅ Authentication flow (signup, login, logout)
5. ✅ Stripe payment integration (test mode)
6. ✅ Email templates ready
7. ✅ Build passes (npm run build works)
8. ✅ Ready to deploy to Vercel

## Success Criteria

The MVP is complete when:
- A new user can sign up, see onboarding, create/manage their data
- Free users hit plan limits and see upgrade prompts
- Stripe checkout works with test cards
- The app looks professional on mobile and desktop
- No TypeScript errors or build failures
- All features work end-to-end

**Start by creating an implementation plan** that breaks down how you'll build this. I'll review it before you proceed.