as.AN ENGINEER’S
FIELD JOURNAL
← Back to the field journal
PROJECT 02 / Tools / independent

gitinit.

Start with the interesting problem.

Backend scaffolding with the integrations, configuration and runnable foundations already connected.

  • TypeScript
  • Next.js
  • Turborepo
Open gitinit Source
git init → something useful⌘
01src/main/java/app/
02  Application.java
03  api/HealthController.java
04  config/DatabaseConfig.java
05src/test/java/app/
06  HealthControllerTest.java
07build.gradle.kts
08Dockerfile
Illustrative file tree · full generation in gitinit
01 / PURPOSE

What it makes possible.

Reduce the repetitive work between choosing a backend stack and writing the first useful feature.

  • Generate Spring services in Java or Kotlin, Flask in Python, and Kratos in Go.
  • Select integrations and inspect the generated file tree before downloading a ZIP.
  • Include adapters, configuration, tests, health checks, Docker setup and runtime documentation.
02 / ARCHITECTURE

Under the surface.

  1. 01

    A typed configuration feeds framework-specific generators in a Turborepo workspace.

  2. 02

    Templates and integration adapters produce a project tree rather than a list of dependencies.

  3. 03

    The web interface previews the tree and packages the generated files into a download.

03 / ENGINEERING DECISIONS

The deliberate choices.

  • Make scaffolding inspectable before download.
  • Treat integrations as working code and configuration, not just package entries.
  • Keep generation stateless so a new service does not require an account.
04 / OUTCOME & STATUS

Where it stands.

A public generator covering three backend ecosystems. The interactive tree here is a simplified illustration; complete projects are generated in gitinit.

Last commit ·

NEXT IN THE JOURNALOOTD