Skip to content
AI PROGRAMMING FRAMEWORK · TG-BOOT

Make AI write right.
Make teams own it.

High-quality AI programming is not about longer prompts. It is about putting engineering constraints into code. TG-boot gives AI and human developers one verifiable boundary: modules, contracts and architecture gates.

1JVM by default
16+backend modules
0business rewrites when splitting
2collaboration tracks
tg-boot / quickstartLIVE

$ git clone https://gitee.com/pub_module/tg-boot.git

$ powershell -ExecutionPolicy Bypass -File scripts\up.ps1

✓ JDK 27 · Maven · MariaDB · Redis ready

✓ runner started on :9999

✓ middle platform on :9100

[ModuleRpc] [LOCAL] ApiSysUserService#getByUserCode

[MQ] system.user.login → parentled

_

LOCAL FIRSTMQ FALLBACKARCH GUARDED
EXECUTABLE PATH

Turn “knowing” into
four finishable actions

You do not need to become a framework expert first. Each step has a clear input, output and acceptance check.

SIX SUPPORTSWhy it holds together

Starter-based capabilities

Add a dependency to assemble; remove it to unload. Business modules do not rebuild infrastructure.

Contracts as boundaries

Cross-module calls only use *-api contracts, DTOs and enums, never another module’s implementation.

AUTO routing

Local provider first, MQ only when needed. The business code stays the same.

Architecture gates

Forbidden dependencies become tests, enforced by CI rather than memory.

One-command environment

JDK, Maven, MariaDB, Redis and Node live under .tools and are prepared by one script.

Split without rewrite

Start as one process. Split by domain later; what changes is deployment, not the business code.

“

AI does not lack the ability to generate code. It lacks a clear boundary of what must not be written. A good framework makes the correct path the easiest path.

TG-boot design principleContract first · boundaries as code
OPEN SOURCE

Run one module first.
Then decide whether to trust it.

OPEN SOURCE · HUMAN COMMUNITY