How to use
Fill in every [PLACEHOLDER] with your specifics before pasting. The more detail you provide, the better the output.
→Fill in every [PLACEHOLDER] — vague inputs give generic outputs
→Works best in Claude Projects with the Full-Stack Architect system prompt active
→If the model stops mid-build, say "Continue from where you left off"
→For Replit: paste in the Agent chat, not the editor
Best platforms
claude.aiGoogle AI StudioReplitbolt.new
The megaprompt
I want to build a SaaS application. Build it completely — front-end, back-end, database, authentication, and payments.
## Product Description
Name: [APP NAME]
What it does: [ONE PARAGRAPH describing the core value proposition]
Target user: [WHO USES THIS and what problem does it solve for them]
Business model: [Freemium / Subscription / Pay-per-use] at [PRICE POINT]
## Tech Stack (use this exactly)
- Framework: Next.js 15 (App Router)
- Styling: Tailwind CSS + shadcn/ui
- Database: Supabase (PostgreSQL)
- Auth: Supabase Auth (email + Google OAuth)
- Payments: Stripe (subscriptions)
- Deployment: Vercel
## Pages to Build (build ALL of these)
1. Landing page with hero, features, pricing, FAQ sections
2. Sign up / Login page (email + Google)
3. Onboarding flow (collect user info, guide to first value)
4. Main dashboard (core product functionality)
5. Settings page (profile, billing, notifications)
6. Admin panel (user management, metrics overview)
## Core Product Features
[List 3-5 specific features of the main product with precise descriptions]
## Database Schema
Users table: id, email, name, avatar, plan (free/pro), created_at
[Add your specific tables here with fields]
## Subscriptions
Free plan: [What's included]
Pro plan: [What's included, price, Stripe price ID]
## Design Requirements
- Clean, modern SaaS aesthetic (think Linear, Notion, Vercel)
- Dark mode support
- Fully responsive — mobile is 40% of your users
- Loading skeletons instead of spinners
- Toast notifications for all user actions
## Build Order
1. Database schema and Supabase setup
2. Auth flow complete
3. Landing page
4. Core product feature (the thing that delivers value)
5. Billing integration
6. Settings page
7. Admin panel
Build each section completely before moving to the next. Show the file path at the top of each file.