saas-scaffolderlisted

# SaaS Scaffolder Skill ## When to activate - Starting a new SaaS product from scratch - Need a production-ready starter with auth, billing, and email wired up - Want to skip boilerplate and start with working infrastructure - Building a proof-of-concept that needs to be shippable ## When NOT to use - Adding a feature to an existing codebase — use the relevant skill directly - Non-SaaS projects (static sites, mobile apps, CLI tools) — use the appropriate skill - When you need fine-grained control over every dependency choice from the start ## Instructions ### Full SaaS scaffold ``` Scaffold a complete SaaS application. Product: [name and one-line description] Stack preferences: - Framework: [Next.js 15 App Router (default) / other] - Auth: [Better Auth (default) / Clerk / NextAuth] - Database: [PostgreSQL + Drizzle (default) / Prisma / MongoDB] - Hosting DB: [Neon (default) / Supabase / PlanetScale] - Payments: [Stripe (default) / Paddle / none] - Email: [Resend (default) / SendGrid / none] - Styling: [Tailwind + shadcn/ui (default)] - Deploy: [Railway (default) / Vercel / Fly.io] Generate: 1. Complete directory structure 2. All configuration files (next.config.ts, drizzle.config.ts, etc.) 3. Database schema for [core entities] 4. Auth setup with Google + email/password 5. Stripe subscription with [plans described] 6. All required .env variables documented 7. First-run setup commands Output as: file tree + key file contents ``` ### Default tech stack