Agents will generate services faster than you can wire them. Local multi-service stacks will be expected to boot in seconds with hot reload, not after an afternoon of Compose/Tiltfile pain. If your setup still depends on a rotting wiki, you’re already behind.
The 10 tools:
- Claude Code / OpenCode / Codex CLI
- TDK CLI
- Cursor (or Zed)
- Bun
- ripgrep + fzf
- lazygit
- Ollama
- gh
- Docker + Tilt
- uv (or mise)
Secret sauce (explained with diagrams)
The other nine tools make individual work faster. TDK CLI is the topology contract. You write one small service.json. TDK generates the Dockerfiles (L1–L4 golden layers), Tilt live-update rules, Traefik routes, health checks, Vite/TS configs, shared Postgres wiring, and the rest. Then tdk up boots it. No Kubernetes on your laptop. Production stays on Helm.
Diagram 1 — 2027 Survival Stack
Agents on top, TDK CLI as the local orchestration layer, Docker + Tilt underneath, terminal multipliers on the sides.
Diagram 2 — The Contract (secret sauce core)
One service.json becomes the entire local runtime.
Diagram 3 — Traditional vs TDK
The friction that dies.
Diagram 4 — Three Subsystems Architecture
How the CLI, Discovery, and Engine actually fit together.
Diagram 5 — Golden Layers + Hot Reload Loop
Why rebuilds stay fast and agents stay productive.
That’s the sauce. Agents generate services. TDK keeps the local topology legible, generated, and one command away from healthy. tdk doctor checks the machine. tdk up replaces the setup wiki.
Install:
curl -fsSL https://tdk-landscape.github.io/install.sh | sh
or npm install -g @tdk-landscape/tdk-cli-core
If your 2027 stack still requires hand-wiring every new service, the gap is about to hurt.
Top comments (0)