prune

Author: spoons-and-mirrors

lib/prompts/prune.md

@@ -1,41 +1,18 @@
-Prunes tool outputs from context to manage conversation size and reduce noise.
+Use this tool to remove tool outputs from context entirely. No preservation - pure deletion.
 
-## IMPORTANT: The Prunable List
+THE PRUNABLE TOOLS LIST
+A <prunable-tools> will show in context when outputs are available for pruning. Each entry follows the format `ID: tool, parameter (~token usage)` (e.g., `20: read, /path/to/file.ts (~1500 tokens)`). You MUST select outputs by their numeric ID. THESE ARE YOUR ONLY VALID TARGETS.
 
-A `<prunable-tools>` list is provided to you showing available tool outputs you can prune when there are tools available for pruning. Each line has the format `ID: tool, parameter` (e.g., `20: read, /path/to/file.ts`). You MUST only use numeric IDs that appear in this list to select which tools to prune.
+THE WAYS OF PRUNE
+`prune` is a blunt instrument for eliminating noise (irrelevant or unhelpful outputs that provide no value), or superseded information (older outputs replaced by newer, more accurate data), wrong target (you read or accessed something that turned out to be irrelevant). Use it judiciously to maintain a clean and relevant context.
 
-## When to Use This Tool
+BE STRATEGIC! Prune is most effective when batched. Don't prune a single tiny output - wait until you have several items (depending on context occupation of those noisy outputs).
 
-Use `prune` for removing individual tool outputs that are no longer needed:
+Do NOT prune when:
+NEEDED LATER: You plan to edit the file or reference this context for implementation.
+UNCERTAINTY: If you might need to re-examine the original, keep it.
 
-- **Noise:** Irrelevant, unhelpful, or superseded outputs that provide no value.
-- **Wrong Files:** You read or accessed something that turned out to be irrelevant.
-- **Outdated Info:** Outputs that have been superseded by newer information.
+Before pruning, ask: _"Will I need this output for upcoming work?"_ If yes, keep it. Pruning that forces re-fetching is a net loss.
 
-## When NOT to Use This Tool
-
-- **If the output contains useful information:** Keep it in context rather than pruning.
-- **If you'll need the output later:** Don't prune files you plan to edit or context you'll need for implementation.
-
-## Best Practices
-
-- **Strategic Batching:** Don't prune single small tool outputs (like short bash commands) unless they are pure noise. Wait until you have several items to perform high-impact prunes.
-- **Think ahead:** Before pruning, ask: "Will I need this output for upcoming work?" If yes, keep it.
-
-## Format
-
-- `ids`: Array of numeric IDs as strings from the `<prunable-tools>` list
-
-## Example
-
-<example_noise>
-Assistant: [Reads 'wrong_file.ts']
-This file isn't relevant to the auth system. I'll remove it to clear the context.
-[Uses prune with ids: ["5"]]
-</example_noise>
-
-<example_superseded>
-Assistant: [Reads config.ts, then reads updated config.ts after changes]
-The first read is now outdated. I'll prune it and keep the updated version.
-[Uses prune with ids: ["20"]]
-</example_superseded>
+THE FORMAT OF PRUNE
+`ids`: Array of numeric IDs (as strings) from the `<prunable-tools>` list