Could you elaborate a bit more? What do you mean by ‘one’ exactly? Maybe I can point you in the right direction. However, there are not a lot of high-quality public guidelines that I know of.

In general, I am afraid that the Serverless paradigm is missing some opinionated patterns that engineers can readily adopt. The free-format-use-everything-in-the-toolbox approach leads to hard-to-maintain solutions (as pointed out in my previous blog https://medium.com/codex/managing-serverless-spaghetti-c2fb1a7db73e). The subjects are not directly related, but I have seen the same thing in the React space. People are given a very powerful tool, but with little opinion, the early adopters end up all over the place. I might have spent too much time on technologies like Spring Boot, Angular, Android, Grails, and have an affection for opinion. But those frameworks emerged like that for a reason.