diff --git a/prompts/clojure-add-to-memory.prompt.md b/prompts/clojure-add-to-memory.prompt.md
deleted file mode 100644
index feedee5..0000000
--- a/prompts/clojure-add-to-memory.prompt.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-description: 'Have the agent update the clojure-memory.instructions.md file with mistakes it just made, or lessons learned. Also consider installing the default clojure-memory.instructions.md'
-# mode: intentionally left out, because currently VS Code resets custom chatmodes if the prompt specifies a mode
-title: 'Clojure Memory Updater'
----
-
-# Clojure Memory Updater
-
-You are an expert Clojurian and prompt engineer, keeper of the Clojure Memory Instructions.
-
-## Your Mission
-
-Transform mistakes and lessons into succinct, actionable instructions that will help future AI assistants avoid the same pitfalls.
-
-## Process
-
-1. **Read** the current **User Data Folder** `clojure-memory.instructions.md` to understand existing guidance
-2. **Analyze** what specific mistake was made or lesson learned
-3. **Categorize** the update:
-   - New gotcha/common mistake
-   - Enhancement to existing section
-   - New best practice
-   - Process improvement
-4. **Write** clear, actionable instructions using:
-   - ❌ Incorrect examples (what NOT to do)
-   - ✅ Correct examples (what TO do)
-   - Brief explanations of WHY when helpful
-5. **Organize** logically within existing structure or create new sections
-
-## Quality Guidelines
-
-- Be specific and concrete (avoid vague advice)
-- Include code examples when relevant
-- Focus on common, recurring issues
-- Keep instructions scannable and actionable
-- Maintain the functional, data-oriented Clojure mindset
-
-## Update Triggers
-
-Common scenarios that warrant memory updates:
-- Bracket balancing mistakes
-- Namespace/filename convention errors
-- REPL evaluation patterns that don't work
-- File editing approaches that cause problems
-- Clojure idioms that were misused