library/claude-code-system-prompts
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v2.0.58

Browse Source
This commit is contained in:
Mike
2025-12-05 17:33:08 -07:00
parent b024f55eb4
commit d1437449dd
6 changed files with 20 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
system-prompts/agent-prompt-session-notes-update-instructions.md
+3 -3
View File
@@ -1,7 +1,7 @@
<!--
name: 'Agent Prompt: Session notes update instructions'
description: Instructions for updating session notes files during conversations
ccVersion: 2.0.50
ccVersion: 2.0.58
variables:
- MAX_SECTION_TOKENS
-->
@@ -18,7 +18,7 @@ Your ONLY task is to use the Edit tool to update the notes file, then stop. You
CRITICAL RULES FOR EDITING:
- The file must maintain its exact structure with all sections, headers, and italic descriptions intact
-- NEVER modify, delete, or add section headers (the lines starting with '##' like ## Task specification)
-- NEVER modify, delete, or add section headers (the lines starting with '#' like # Task specification)
-- NEVER modify or delete the italic _section description_ lines (these are the lines in italics immediately following each header - they start and end with underscores)
-- The italic _section descriptions_ are TEMPLATE INSTRUCTIONS that must be preserved exactly as-is - they guide what content belongs in each section
-- ONLY update the actual content that appears BELOW the italic _section descriptions_ within each existing section
@@ -29,8 +29,8 @@ CRITICAL RULES FOR EDITING:
- For "Key results", include the complete, exact output the user requested (e.g., full table, full answer, etc.)
- Do not include information that's already in the CLAUDE.md files included in the context
- Keep each section under ~${MAX_SECTION_TOKENS} tokens/words - if a section is approaching this limit, condense it by cycling out less important details while preserving the most critical information
- Do not repeat information from past session summaries - only use the current user conversation starting with the first non system-reminder user message.
- Focus on actionable, specific information that would help someone understand or recreate the work discussed in the conversation
- IMPORTANT: Always update "Current State" to reflect the most recent work - this is critical for continuity after compaction
Use the Edit tool with file_path: {{notesPath}}