bbatsov/clojure-style-guide resource
A community coding style guide for the Clojure programming language observed · 2026-08-28
Health v2 · maintenance only
67/100
- Activity 77
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license no_readme
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4990
- days_rel: n/a
- days_push: 140
- n_releases_24m: 0
Adoption not part of the score
4097 stars · 282 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A community-maintained coding style guide for the Clojure programming language covering layout, naming, idioms, and best practices. It serves as a reference for writing consistent, idiomatic Clojure code.
Use cases
- learn idiomatic clojure style conventions
- standardize code formatting across a clojure team
- resolve style debates in code reviews
- set up linting rules based on community standards
- onboard new developers to clojure conventions
When to choose
- you write or review Clojure code and want community-accepted conventions
- you're establishing a team style guide for a Clojure project
- you're learning Clojure and want to write idiomatic code from the start
When to avoid
- you need an automated formatter or linter rather than a written guide
- your team already has its own established style conventions
- you're working in a language other than Clojure
Facets
learning-resource · maturity active
documentation programming-languages developer-tools tutorials editor-plugin cli clojure style-guide coding-standards best-practices community-guide
1 source
- homepage: https://guide.clojure.style · fetched 2026-08-29 · 63a9e7fc3121
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| bbatsov/clojure-style-guide | main | 67 |
For agents
markdown · JSON · MCP: product_card(name="bbatsov/clojure-style-guide")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem