Thanks for the response, appreciate your project. However this is what I meant by redesign your service - I think that when writing in a language, in this case Go, it's important to keep the idioms of the langauge. Part of the most critical idiom (IMO) is the packages' names, it's not just a name, it's something that defines what this package provide, you need to tell that your package contains functionality related to account, not that this package contains services, or use-cases. See the section for the screaming-architecture.

Again, it's all just an opinion, I agree with this very much, but I understand that there will always be other ones...