Is there an idiomatic Haskell?

Hi there! I’m starting a company, I’m using Haskell and I’m happy with it. Things are going good, the features I develop work, I write tests, everything feels in place, I’ve got no complaints about my current workflow, or the language, or the ecosystem (perhaps about tooling, it was non-trivial to set up my CI/CD pipeline, but that’s a subject for another topic). The thing is, I’ve never worked with another Haskell developer before, so I’m just doing things my way. Although that’s fine, sometimes I wonder if I’m doing things the “correct” way. (I know it’s very hard to define correctness in software engineering). Other languages I’ve used have some agreed upon practices that almost everybody using them follow. I wonder if Haskell has the same. I think one of the beauties of this language is the freedom it gives one to do anything they want in any way they please, but with it comes the feeling that “there may be a better way to do this” all the time. Usually I’m happy if the artifact does what I want it to do under production loads, but I digress. Is there a way to write Haskell that I can expect to see if I start reading codebases out there? Or is it common for each project or company to develop a style?