I got tired of rebuilding the same stack for every project

Every time I started a new project, I found myself doing the same thing: setting up the framework, auth, database, storage, caching, Docker, CI, and all the little pieces that make a project ready for actual development.

Initially, I wanted a starter template I could reuse. But I kept running into another problem: not every project needs the same stack.

Sometimes I want Next.js or TanStack Start. Other times, I want React + Vite on the frontend with a separate backend. I don't want to maintain a completely different boilerplate for every combination.

That's why I built Clubedge Starter and its CLI, @clubedge/create-clubedge-app.

The idea has evolved beyond cloning a repository. You can choose your stack, configure the modules you need, and scaffold a project around those choices rather than inheriting a fixed architecture.

I've also built an interactive builder so you can explore the available combinations before generating a project.

• CLI: https://github.com/Clubedge/create-clubedge-app

• Interactive builder: https://starter.clubedge.live/builder

• Documentation: https://starter.clubedge.live/docs

It's Apache-2.0 licensed and completely open source.

I'm curious about one thing: if you were building a tool like this, would you prefer a highly configurable scaffold that supports different frontend/backend combinations, or separate, opinionated starters for each stack? That's one of the design decisions I'm trying to get right.