// the find
mckaywrigley/mckays-app-template
This is the template I use to start new full-stack projects.
A personal Next.js SaaS starter from Mckay Wrigley, wiring together Supabase/Drizzle for data, Clerk for auth, and Stripe for payments. It's for someone who wants the tedious account/billing/DB plumbing already connected so they can start on actual product code on day one.
The route-group structure ((authenticated)/(unauthenticated)) cleanly separates logged-in app pages from marketing/auth pages, which is the right call in App Router and saves you from reinventing that split. Stripe webhook handling and a customers table/schema are already wired end-to-end, which is normally the most annoying integration to get right. Drizzle + Supabase gives you real migrations and typed queries instead of a loose ORM-less setup.
Zero tests anywhere in the tree — for a template meant to be the foundation of someone else's production app, that's a real gap. The README is just an install checklist; there's no explanation of why these services were chosen or how to swap one out, and it funnels you toward the author's paid workshop for the actual reasoning. You're locked into three paid vendors (Clerk, Stripe, Supabase) from the start, so ripping one out later means touching auth middleware, schema, and billing code simultaneously. No CI config in the repo, so there's nothing enforcing that the template itself stays in a working state as dependencies update.