AI Prompts

Set up this SaaS starter: install dependencies, create .env from .env.example,
set up the PostgreSQL database with Prisma, and run the dev server.
Walk me through each step.

Help me deploy this Next.js SaaS to Vercel: walk me through every step
including GitHub push, Vercel import, all environment variables I need to set,
custom domain setup, and the post-deploy checklist (Stripe webhook, Clerk webhook).

Deploy this SaaS to Railway: create the project, add PostgreSQL,
set all environment variables, configure the custom domain,
and set up the Stripe webhook endpoint.

Create a production Dockerfile (multi-stage: deps → build → runner with node:20-alpine)
and docker-compose.yml (app + PostgreSQL) for self-hosted deployment.
Include nginx reverse proxy config.

Set up GitHub Actions CI/CD for this Next.js project:
lint, type-check, and build on every PR.
Deploy to Vercel on merge to main.

Add a "Projects" feature to this SaaS:
1. Create a Project model in Prisma (name, description, userId, createdAt)
2. Add relation to User model
3. Create dashboard page at /dashboard/projects with list view
4. Add create/edit/delete functionality
5. Add the Projects nav item to the sidebar
6. Enforce plan limits from PLANS config (free=1, pro=10, business=unlimited)
7. Add loading and empty states

Add team support to this SaaS:
1. Create Team and TeamMember models in Prisma
2. Users can create teams and invite members by email
3. Team dashboard at /dashboard/team
4. Team settings (rename, manage members, roles)
5. Projects can belong to a team or a user
6. Team billing (one subscription per team)

There's already an ApiKey model in Prisma. Build the UI for it:
1. Create /dashboard/settings/api-keys page
2. Users can create API keys with a name
3. Show the key only once on creation
4. List all keys with last used date
5. Revoke (delete) keys
6. Add API key auth middleware for /api/v1/* routes

Add usage tracking to enforce plan limits:
1. Create a Usage model (userId, type, count, month)
2. Track API calls per user per month
3. Create a middleware that checks usage before API calls
4. Show usage stats on the dashboard (progress bar vs plan limit)
5. Send email warning at 80% usage
6. Block requests at 100% with upgrade prompt

Add an onboarding wizard after sign-up:
1. Create /dashboard/onboarding with 3 steps
2. Step 1: Complete profile (name, avatar)
3. Step 2: Choose plan (show pricing cards)
4. Step 3: Create first project
5. Store onboarding status on User model
6. Redirect to onboarding if not completed
7. Skip button on each step

Add a contact form to the landing page:
1. Create a ContactMessage model in Prisma
2. Add contact section to the landing page (or /contact page)
3. Form: name, email, message
4. Validate with Zod
5. Save to database
6. Send notification email via Resend to admin
7. Show success toast
8. Add rate limiting (5 per hour per IP)

Add a changelog page:
1. Create content/changelog/ directory for MDX files
2. Create lib/changelog.ts (similar to lib/blog.ts)
3. Create /changelog page listing all entries
4. Each entry: version, date, title, content
5. Add "What's new" badge in dashboard linking to changelog

Add an in-app notification system:
1. Create Notification model (userId, title, message, read, type, createdAt)
2. Bell icon in dashboard header with unread count badge
3. Dropdown showing recent notifications
4. Mark as read on click
5. /dashboard/notifications page for full list
6. Send notifications on: subscription change, approaching limits, system updates

Add file upload with cloud storage:
1. Install and configure uploadthing or AWS S3
2. Create upload API route
3. Add file upload component in dashboard
4. Store file URLs in database
5. Image preview and download
6. Plan-based storage limits

Rebrand this SaaS for a [DESCRIBE YOUR PRODUCT] product:
1. Change app name to "[NAME]" in .env
2. Update primary color to [COLOR] in globals.css
3. Rewrite landing page copy: hero headline, subheading, features, FAQ
4. Update pricing plan names and features to match my product
5. Update meta descriptions for SEO

Change the pricing plans to:
- Starter: free, 3 projects, 500 API calls/month
- Growth: $49/month ($490/year), 25 projects, 50K API calls
- Scale: $199/month ($1990/year), unlimited everything
Update PLANS in lib/stripe.ts, the pricing component,
and tell me what Stripe products/prices to create.

Translate the entire UI from French to English:
- Landing page (hero, features, pricing, FAQ, header, footer)
- Dashboard (sidebar, pages, settings, billing)
- Auth pages
- Email templates
- Error messages and toasts
- Blog post
Keep variable names and code comments in English.

Add a testimonials section to the landing page between Features and Pricing:
- 6 testimonial cards in a 3-column grid
- Each: avatar, name, role, company, quote text
- Star rating
- Subtle card design matching existing UI
- Generate realistic fake testimonials for a SaaS tool

The Stripe webhook at /api/webhooks/stripe isn't working. Help me debug:
1. Check the route handler code for errors
2. Verify STRIPE_WEBHOOK_SECRET is correct
3. Test locally with `npm run stripe:listen`
4. Check that all 4 events are handled
5. Verify the user update logic matches the Prisma schema

Users aren't being synced to the database after sign-up. Debug:
1. Check if Clerk webhook is configured
2. Check /api/webhooks/clerk route handler
3. Verify the syncUser() function in lib/auth.ts
4. Check if the dashboard layout calls syncUser() as fallback
5. Check Prisma connection and User model

The build is failing. Help me fix it:
1. Run npm run build and show me the errors
2. Check for TypeScript type errors
3. Check for missing environment variables (getStripe() and getResend() handle this)
4. Check for import issues
5. Fix all errors and verify the build passes

In addition to subscriptions, add one-time payment support:
1. Add a "credits" or "tokens" field to the User model
2. Create a /api/stripe/buy-credits route
3. Stripe Checkout in payment mode (not subscription)
4. Webhook handler for one-time payments
5. Dashboard showing credit balance
6. Deduct credits on API usage

Enhance the admin panel with real analytics:
1. Add chart library (recharts or chart.js)
2. Revenue chart (daily/weekly/monthly)
3. User growth chart
4. Churn rate tracking
5. Plan distribution pie chart
6. Export data to CSV

Convert this SaaS to multi-tenant architecture:
1. Add Organization model
2. Users belong to organizations
3. Data scoped by organization
4. Organization-level billing
5. Org settings and member management
6. Subdomain or path-based routing per org