I got tired of re-wiring the same boilerplate on every project so I built ForgeKit

#webdev #cli #typescript #opensource

New project. Blank repo and here I am again, writing the same Dockerfile I wrote last month.
Same GitHub Actions. Same ESLint config. Same docker-compose. Same test setup.

I've done this so many times I could do it in my sleep. Which is exactly why I stopped doing it.

I built ForgeKit. Run one command and your project is production-ready before you've had your first coffee.

npm install -g forgekit-cli
forgekit new my-app --template web-app

13 files. TypeScript configured. ESLint ready. Dockerfile written. docker-compose working. GitHub Actions running on your first push. Vitest set up. Nothing left to wire.

You write code. Not config.

What's included

⚡ CI/CD from commit one

GitHub Actions wired and passing before you even open a PR.

📦 Docker, done

Dockerfile and docker-compose ready to run locally and in prod.

✅ Tests configured

Vitest is set up. You just write the tests.

📋 6 battle-tested templates

Next.js, FastAPI, Go, ML pipeline, Serverless, and more.

Pick your stack

web-app: Node.js + React + TypeScript
api-service: Python + FastAPI + PostgreSQL + Docker
ml-pipeline: Python + Jupyter + MLflow
next-app: Next.js + Tailwind + TypeScript
go-api: Go + Gin + PostgreSQL
serverless: AWS Lambda + TypeScript

"Can't I just clone a starter template?"

A starter template gives you files. ForgeKit gives you a working engineering setup. CI runs on push. Docker builds locally. Linting catches issues before they hit your PR. Security scanning runs automatically.

The first time you git push on a ForgeKit project, everything just works.