clojure

Clojure Style Guide

The community Clojure style guide — best practices for writing readable, idiomatic Clojure that other Clojurists can maintain.

Quick Decision: What do you need?

Task	Go to
Line length, indentation, alignment, brackets, blank lines, ns form structure, namespace naming	source-layout.md
Naming functions, vars, protocols, records, predicates, dynamic vars, constants, unused bindings	naming.md
Threading macros, when/if, if-let, cond/condp/case, sets as predicates, Java interop, data structures, mutation, strings, exceptions	idioms.md
Function length, arity ordering, positional params, pre/post conditions, higher-order fns, macros	functions-macros.md
Comment syntax (;;;; / ;;; / ;; / ;), #_, docstrings, metadata (:added, :deprecated, :see-also, :no-doc)	documentation.md
Test directory layout, namespace naming, deftest naming, testing blocks, are, match?, exceptions	testing.md

Core Principles

• Optimize code for human consumption — readability over cleverness.
• Consistency within a project matters more than strict adherence to this guide.
• Use clj-kondo for linting and cljfmt/cljstyle for formatting.
• Prefer functional style; use mutation only when it makes sense.