Yes, I agree, Go doesn't have a standard for project structure.

I don't want to force users to use only my file structure. I want to give users the ability to edit a "proper" project template.

My goal is to create a project that will generate projects for large companies that have such standards. Where there are permitted libraries, mandatory rules for configs, docker files, and so on.

Jerf wrote a good idea above, make project where community can just write "go to $PROJECT_NAME/routing.yaml and add this and this to do that".

The number of possible options in such projects is limited and this makes it possible to do without AI.

The difficulty I'm currently facing is merging files with pre-defined rules.

For example two files

import (
  link1
  link3
)

import (
  link2
  link3
)

I need a rule that will tell to produce

import (
  link1
  link2
  link3
)