How do I install the Clojure skill?

Run npx skillmds@latest add anntnzrb/clojure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Clojure skill do?

Use when Clojure, ClojureScript, deps.edn, REPL, spec, macros, or functional code are involved. It is listed under Coding & Dev Tools on SkillMD.

Is Clojure safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clojure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clojure free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under AGPL-3.

Who published Clojure?

anntnzrb (@anntnzrb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clojure by anntnzrb — Agent Skill

Name: Clojure
Rating: 4.2 (5 reviews)
Author: anntnzrb

File contents

Clojure Development

Focus: functional Clojure; deps.edn, tools.deps, immutability.

Workflow

1. MODEL    -> Define data with maps, records, specs
2. COMPOSE  -> Build with pure functions, ->> threading
3. TEST     -> Write tests first (clojure.test or Kaocha)
4. VALIDATE -> clojure -M:test/run && clj-kondo --lint src
5. ITERATE  -> Refactor in REPL, keep functions pure

CLI

# Project setup
clojure -Tnew app :name myuser/myapp    # New app project
clojure -Tnew lib :name myuser/mylib    # New library

# Run
clojure -M -m myapp.core                # Run -main
clojure -M:run                          # Via alias
clojure -X:run                          # Exec function

# REPL
clj                                     # Basic REPL
clojure -M:repl/rebel                   # Rebel readline

# Test
clojure -X:test/run                     # Run tests (Kaocha)
clojure -M:test -m kaocha.runner        # Alternative

# Build
clojure -T:build uber                   # Uberjar
clojure -T:build jar                    # Library jar

# Dependencies
clojure -X:deps tree                    # Dependency tree
clojure -X:deps find-versions :lib clojure.java-time/clojure.java-time
clojure -M:search/outdated              # Find outdated deps

Notes

Project layout, deps.edn templates, core patterns, naming conventions, anti-patterns: reference.md.

Engineering checks

Normalize untrusted input once at the boundary; use clojure.spec only when validation or generation pays for itself.
Preserve error context with ex-info and structured ex-data; NEVER catch-and-forget failures.
Keep side effects, resource ownership, cancellation, and cleanup at the edge; keep core transformations pure.
Test observable behavior and failure paths with deterministic values; avoid pinning private implementation shape.
Introduce helpers, protocols, or abstractions only for concrete reuse or boundary needs.

Research Tools

# gh search code for real-world Clojure patterns
gh search code "(go-loop [" --language=clojure
gh search code "(comp (map" --language=clojure
gh search code "(s/def ::" --language=clojure

Required follow-up reads

Need	Read	When
Core language/project reference	`reference.md`	For data structures, idioms, errors, layout, or `deps.edn`
Functional patterns	`cookbook/patterns.md`	For sequences, transducers, maps, reducers, or zippers
Concurrency	`cookbook/concurrency.md`	For atoms, refs, agents, dynamic vars, `core.async`, futures, or promises
Specs	`cookbook/spec.md`	For validation, conforming, generators, or function instrumentation
Testing	`cookbook/testing.md`	For `clojure.test`, Kaocha, fixtures, async tests, or test.check
Macros	`cookbook/macros.md`	Only when a function cannot express the required compile-time transformation

---name: clojuredescription: Use when Clojure, ClojureScript, deps.edn, REPL, spec, macros, or functional code are involved.license: AGPL-3.0-or-later---# Clojure DevelopmentFocus: functional Clojure; `deps.edn`, `tools.deps`, immutability.## Workflow```1. MODEL -> Define data with maps, records, specs2. COMPOSE -> Build with pure functions, ->> threading3. TEST -> Write tests first (clojure.test or Kaocha)4. VALIDATE -> clojure -M:test/run && clj-kondo --lint src5. ITERATE -> Refactor in REPL, keep functions pure```## CLI```bash# Project setupclojure -Tnew app :name myuser/myapp # New app projectclojure -Tnew lib :name myuser/mylib # New library# Runclojure -M -m myapp.core # Run -mainclojure -M:run # Via aliasclojure -X:run # Exec function# REPLclj # Basic REPLclojure -M:repl/rebel # Rebel readline# Testclojure -X:test/run # Run tests (Kaocha)clojure -M:test -m kaocha.runner # Alternative# Buildclojure -T:build uber # Uberjarclojure -T:build jar # Library jar# Dependenciesclojure -X:deps tree # Dependency treeclojure -X:deps find-versions :lib clojure.java-time/clojure.java-timeclojure -M:search/outdated # Find outdated deps```## NotesProject layout, deps.edn templates, core patterns, naming conventions, anti-patterns: `reference.md`.## Engineering checks- Normalize untrusted input once at the boundary; use `clojure.spec` only when validation or generation pays for itself.- Preserve error context with `ex-info` and structured `ex-data`; NEVER catch-and-forget failures.- Keep side effects, resource ownership, cancellation, and cleanup at the edge; keep core transformations pure.- Test observable behavior and failure paths with deterministic values; avoid pinning private implementation shape.- Introduce helpers, protocols, or abstractions only for concrete reuse or boundary needs.## Research Tools```# gh search code for real-world Clojure patternsgh search code "(go-loop [" --language=clojuregh search code "(comp (map" --language=clojuregh search code "(s/def ::" --language=clojure```## Required follow-up reads|Need|Read|When||---|---|---||Core language/project reference|`reference.md`|For data structures, idioms, errors, layout, or `deps.edn`||Functional patterns|`cookbook/patterns.md`|For sequences, transducers, maps, reducers, or zippers||Concurrency|`cookbook/concurrency.md`|For atoms, refs, agents, dynamic vars, `core.async`, futures, or promises||Specs|`cookbook/spec.md`|For validation, conforming, generators, or function instrumentation||Testing|`cookbook/testing.md`|For `clojure.test`, Kaocha, fixtures, async tests, or test.check||Macros|`cookbook/macros.md`|Only when a function cannot express the required compile-time transformation|

Frequently asked questions

Clojure