clojure-writelisted

# Clojure Development Skill ## Tool Preference When `clojure-mcp` tools are available (e.g., `clojure_eval`, `clojure_edit`), **always use them** instead of shell commands like `./bin/mage -repl`. The MCP tools provide: - Direct REPL integration without shell escaping issues - Better error messages and feedback - Structural Clojure editing that prevents syntax errors Only fall back to `./bin/mage` commands when clojure-mcp is not available. # Autonomous Development Workflow - Do not attempt to read or edit files outside the project folder - Add failing tests first, then fix them - Work autonomously in small, testable increments - Run targeted tests, and lint continuously during development - Prioritize understanding existing patterns before implementing - Don't commit changes, leave it for the user to review and make commits # Metabase Clojure Style Guide This guide covers Clojure and ClojureScript coding conventions for Metabase. See also: `CLOJURE_STYLE_GUIDE.adoc` for the Community Clojure Style Guide. ## Naming Conventions **General Naming:** - Acceptable abbreviations: `acc`, `i`, `pred`, `coll`, `n`, `s`, `k`, `f` - Use `kebab-case` for all variables, functions, and constants **Function Naming:** - Pure functions should be nouns describing the value they return (e.g., `age` not `calculate-age` or `get-age`) - Functions with side effects must end with `!` - Don't repeat namespace alias in function names **Destructuring:** - Map destructuring should use kebab-