Hey Bro 👋

First off, thanks for this repo — it’s a great starting point for new Go projects.

That said, I noticed the presence of a domain-specific package (medicine). While I understand it’s meant to serve as a concrete example of how to structure the project, I think including this kind of domain logic in a boilerplate might backfire.

Here’s why:

• It introduces domain-coupled bloat — anyone adopting the repo as-is will carry over irrelevant logic.
• Inertia risk — some of that code might stay forever, even in unrelated projects, just because it was there from the start. (Following repo as example: https://github.com/gbrayhan/ia-boilerplate-go)
• Harder onboarding — new devs might think medicine is a required part of the architecture.

I’d suggest abstracting the example or moving it to a docs/examples section instead. That way, the repo stays lean and more adaptable to any domain.

Curious to hear what others think — happy to help shape a PR if it makes sense.