This Next.js + NestJS starter made me 10x faster

Every new project used to begin the same way.

I'd create a Next.js app, set up a NestJS backend, configure TypeScript, install Tailwind and shadcn/ui, add ESLint and Prettier, organize the monorepo, and wire up CI/CD. By the time everything was ready, I'd already spent hours without building a single feature.

Eventually, I realized I was solving the same problem over and over again.

Turning repetition into a template

Instead of repeating the setup for every side project or client application, I decided to package my preferred stack into a reusable starter.

That's how next-nest-template is created.

It combines the tools I reach for most—Next.js, NestJS, TypeScript, Tailwind CSS, Prisma, Shadcn UI and Clerk Auth into a clean foundation that's ready to build on from day one.

Why I built it

The goal isn't to create another boilerplate for the internet. It is to make my workflow faster.

I wanted to spend less time configuring projects and more time designing APIs, building interfaces, and shipping ideas. Having a reliable starting point means I can focus on solving real problems instead of copying the same configuration files between repositories.

What's included

• Turborepo monorepo with Bun workspaces
• NestJS API with global validation, Clerk auth guard, and user sync
• Next.js 16 App Router with landing page, protected dashboard, and shadcn/ui sidebar
• Clerk authentication on frontend (middleware) and backend (JWT verification)
• Prisma 7 with PostgreSQL adapter, migrations, and Docker Compose for local dev
• Shared types package with class-validator DTOs used by API controllers and server actions
• Dark mode with theme toggle
• Server actions pattern for authenticated API calls from Next.js

Tech stack

The payoff

Now, whenever I start something new, I don't begin with an empty folder. I start with a setup I already trust.

It's a small change, but it has made building products much more enjoyable and a lot faster.