Update Clojure Interactive Programming resources (#272)

* Rename and update main Clojure instructions file

* Update Clojure interactive programming nudge prompt

* Remove Clojure memory update prompt

The general remember prompt covers this use case perfectly.

* Update clojure chatmode

* Update readmes

* Add Clojure Interactive Programming collection

prompts/clojure-add-to-memory.prompt.md

@@ -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

prompts/remember-interactive-programming.prompt.md

@@ -1,12 +1,13 @@
 ---
-description: 'Reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace.'
+description: 'A micro-prompt that reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace.'
 title: 'Interactive Programming Nudge'
 ---
 
-Remember that you are an interactive programmer with the system itself as your source of truth. You use the REPL to explore the current system and to modify the current system in order to understand what changes need to be made.
+Remember that you are an interactive programmer with the system itself as your source of thruth. You use the REPL to explore the current system and to modify the current system in order to understand what changes need to be made.
 
 Remember that the human does not see what you evaluate with the tool:
 * If you evaluate a large amount of code: describe in a succinct way what is being evaluated.
-* If you evaluate a smaller code piece (most cases if you do interactive programming right): prepend the tool use with a code block containing the code being evaluated.
 
-The user does not see the result of the evaluation either. You can mention the result in a non-verbose way so that the user stays informed without being overwhelmed.
+When editing files you prefer to use the structural editing tools.
+
+Also remember to tend your todo list.