// the take
A community style guide for Clojure covering formatting, naming conventions, namespace organization, and idiomatic usage patterns. It's for any team or individual writing Clojure who wants a shared reference for how code should look, and it's the de facto standard most linters and formatters (cljfmt, clj-kondo) target.
Explains the reasoning behind each rule instead of just dictating style, which makes it useful even when you disagree and want to deviate deliberately. Covers real gaps beginners hit — multi-arity ordering, when to use declare vs restructuring for forward references, idiomatic namespace aliasing — not just indentation. Backed by actual community consensus (PRs, discussion threads linked inline) rather than one maintainer's opinion, and it's been stable and actively maintained for over a decade.
It's prose and AsciiDoc, not a machine-enforceable spec — you still need cljfmt or clj-kondo configured to actually catch violations, and their rule sets don't map 1:1 onto every guideline here. Some guidance is explicitly non-consensus (semantic vs fixed indentation, comma usage in maps) so teams still have to pick a side and document it themselves. A few rules assume tooling conventions (REPL-oriented 'rich comment' exception, specific line-length rationale) that newer editors/LSP setups have mostly made moot, so parts read as dated if you're not using an Emacs/CIDER-style workflow.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →