I do not know but on my project I created a separate .domain ns with specs so that I could share them with multiple namespaces and it is nice not to have it all through the core ns. So it works for me 🙂

Thanks! I was reading a few posts and it seems there isn't really a one "correct" way of doing things

sharing specs between namespaces is the reason I'm thinking of doing it as well, and it probably makes sense for s/fdef specs to remain next to their respective functions

I personally put specs above the code, in the same namespace. It makes sense that logically, if I want to see the "Event" spec, it would be in the event.clj namespace for example

I also have a common.clj namespace, which contains shared functions. It also contains common specs, like ::timestamp, which is used in many places

I’d say it can make sense for libraries at a certain scale… though even there you may just want to put them where you need them. For an application you’ll inevitably end up wanting to spread things out.

They don't need to correspond to actual namespaces, the main thing is I guess readability.