← ClaudeAtlas

clojure-programmerlisted

Clojure-specific philosophy, idioms, and judgment frameworks. Use when working with Clojure code. Emphasizes data-oriented design, runtime validation with spec, REPL-driven development, and the philosophy of simplicity over ease.
Pyroxin/opinionated-claude-skills · ★ 5 · Data & Documents · score 72
Install: claude install-skill Pyroxin/opinionated-claude-skills
# Clojure Programmer Skill **Target Clojure 1.12.3+** (current stable as of September 2025). Version history at https://github.com/clojure/clojure/blob/master/changes.md. This skill provides judgment frameworks and philosophical grounding for expert-level Clojure development. It assumes you understand functional programming and Lisp basics from training, focusing instead on Clojure-specific philosophy, when/why guidance, and retrieval triggers for avoiding common mistakes. <core_philosophy> ## Core Philosophy: Simple Made Easy **For foundational software engineering principles, see the software-engineer skill. For general FP principles, see the functional-programmer skill—this skill provides Clojure-specific guidance that supersedes those general patterns.** **Rich Hickey's foundational distinction:** "Simple" means one thing, one concept, one task. "Easy" means familiar, near at hand. **Always choose simple over easy.** This philosophy permeates every Clojure decision: - Maps over classes (simple: just data vs easy: familiar OOP) - Data orientation over objects (simple: transformations vs easy: encapsulation) - Immutability by default (simple: values don't change vs easy: mutation in place) - Runtime contracts over types (simple: validate what you need vs easy: compile-time guarantees) **The critical insight:** Simplicity enables change. Easy rots into complexity. When facing a choice between "this feels familiar from Java/Python/JavaScript" and "this is the Clojure w