Agent skill · software engineering · alirezarezvani
saas-scaffolder
Use when starting a new SaaS app with auth, database, Stripe billing and a dashboard (Next.js App Router, TypeScript, Tailwind, shadcn/ui, Drizzle). Bootstraps it with project_bootstrapper.py.
Why this skill is useful
Generates a complete SaaS project boilerplate with executable code for authentication, database schemas, and billing integration, which the AI cannot generate on its own.
What it needs
Requires drizzle-orm, next, stripe, tailwindcss, typescript installed locally. Requires stripe account access. About 5k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
SaaS Scaffolder Tier: POWERFUL Category: Product Team Domain: Full-Stack Development / Project Bootstrapping --- Input Format --- File Tree Output --- Key Component Patterns Auth Config (NextAuth) Database Schema (Drizzle + NeonDB) Stripe Checkout Route Middleware Environment Variables Template --- Scaffold Checklist The following phases must be completed in order. Validate at the end of each phase before proceeding. Phase 1 — Foundation [ ] 1. Next.js initialized with TypeScript and App Router [ ] 2. Tailwind CSS configured with custom theme tokens [ ] 3. shadcn/ui installed and configured [ ] 4. ESLint + Prettier configured [ ] 5. .env.example created with all required variables ✅ Validate: Run npm run build — no TypeScript or lint errors should appear. 🔧 If build fails: Check tsconfig.json paths and that all shadcn/ui peer dependencies are installed. Phase 2 — Database [ ] 6. Drizzle ORM installed and configured [ ] 7. Schema written (users, accounts, sessions, verificationtokens) [ ] 8. Initial migration generated and applied [ ] 9. DB client singleton exported from lib/db.ts [ ] 10. DB connection tested in local environment ✅ Validate: Run a simple db.select().from(users) in a test script — it should return an empty array without throwing. 🔧 If DB connection fails: Verify DATABASEURL format includes ?sslmode=require for NeonDB/Supabase. Check that the migration has been applied with drizzle-kit push (dev) or drizzle-kit migrate (prod). Phase 3 — Authentication [ ] 11. Auth provider installed (NextAuth / Clerk / Supabase) [ ] 12. OAuth provider configured (Google / GitHub) [ ] 13. Auth API route created [ ] 14. Session callback adds user ID and subscription status [ ] 15. Middleware protects dashboard routes [ ] 16. Login and register pages built with error states ✅ Validate: Sign in via OAuth, confirm session user has id and subscriptionStatus. Attempt to access /dashboard without a session — you should be redirected to /login. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/saas-scaffolder--7e5097