go-archetype.dev

What It Is

go-archetype is a project blueprint and template generation tool. Its core goal is to help teams turn a real, runnable base project into an archetype, then let developers quickly generate new projects from it. The tool itself is written in Golang, but it is not limited to Go projects; the collected material explicitly says it can be used for templates in Golang, JavaScript, Java, Python, and essentially any language.

Core Capabilities

Its design revolves around two roles: blueprint creators, usually senior developers or architects, who create the base project and write transformations.yml; and regular developers, who run the command, answer prompts, and generate a new project. Compared with tools like Cookiecutter, where templates often need to be written in a specific meta-language, go-archetype’s key difference is that the template itself remains valid code in its native language, while transformations are defined separately in a rules file.

transformations.yml contains inputs and transformations. Inputs support text, yesno, and select; they can be prompted interactively or passed in via CLI arguments, which is useful for automation. Template rendering uses Go text/template and includes sprig, supporting string helpers such as upper, lower, snakecase, camelcase, kebabcase, and wrap. For transformers, the source text mentions include and replace; include can conditionally include or exclude entire files or file fragments.

Pricing and Ecosystem

The collected text does not provide pricing, license, installation, or commercial support information, so it is not possible to determine whether the project is open source or closed source, or what its pricing model is. On the ecosystem side, only a GitHub example project link is visible, along with usage notes for Go template and sprig; there is no mention of IDE, CI/CD, package manager, or cloud service integrations.

Pros and Cons

The main advantage is its clear concept: using a real project as the blueprint reduces the cognitive overhead of maintaining templates. CLI-based input is also helpful for scripted project generation. The downside is that the public information is incomplete: installation, version maintenance, licensing, and the full list of transformers are missing from the main text. The documentation also contains multiple spelling errors, which hurts credibility. Its transformation model appears fairly lightweight, so for complex code generation scenarios it may not be as capable as more mature scaffolding ecosystems.

Who It’s For and Access from China

It is suitable for teams that need to standardize microservices, library projects, or internal engineering skeletons, as well as architects who want to codify project best practices. Access from China cannot be determined from the text alone, so it should be marked as unknown. If access is limited, alternatives such as Cookiecutter, Yeoman, Copier, and Hygen may be worth considering.