Skip to content

Instantly share code, notes, and snippets.

@dpaluy

dpaluy/reflext.md

Created August 22, 2025 13:06
Show Gist options
  • Save dpaluy/c150a085326adc7e8e7bffe93524e852 to your computer and use it in GitHub Desktop.
Save dpaluy/c150a085326adc7e8e7bffe93524e852 to your computer and use it in GitHub Desktop.
Download ZIP
Claude Command - Reflect for continues improvement
Raw
reflext.md

Reflect on Conversation

Analyze our conversation history and suggest improvements to CLAUDE.md based on patterns, feedback, and lessons learned.

Process

  1. Review Conversation History

    • Analyze all user feedback and corrections
    • Identify moments where instructions weren't followed
    • Note any repeated issues or preferences

  2. Identify Improvement Opportunities

    • Look for patterns that could be addressed with better instructions
    • Find gaps in current CLAUDE.md that led to misunderstandings
    • Consider user preferences that emerged during interaction

  3. Generate Specific Improvements

    • Create actionable, specific edits for CLAUDE.md
    • Focus on preventing similar issues in future interactions
    • Prioritize changes that address user feedback directly

  4. Present Suggestions

    • Show proposed changes using diff-style format
    • Explain the reasoning behind each suggestion
    • Group related improvements together

  5. Apply Changes (if approved)

    • Ask user: "Would you like me to apply these improvements to CLAUDE.md?"
    • If yes, use Edit tool to update CLAUDE.md
    • Confirm changes were applied successfully

Guidelines

  • Only suggest improvements that genuinely enhance Claude's behavior
  • Keep suggestions specific and actionable, not vague principles
  • Don't suggest redundant rules that duplicate existing instructions
  • Focus on patterns, not one-off incidents
  • Maintain the existing structure and style of CLAUDE.md

Example Output Format


ℹ️ I've identified these improvement opportunities:

### 1. Error Handling Preference
**Current gap**: No guidance on error handling style
**Proposed addition**: "Always use try-catch blocks with specific error types rather than generic catches"
**Reasoning**: You corrected this pattern 3 times during our session

### 2. Import Organization
**Current gap**: No import organization rules
**Proposed addition**: "Group imports by: 1) External packages, 2) Internal modules, 3) Types"
**Reasoning**: You consistently reorganized imports this way

Would you like me to apply these improvements to CLAUDE.md?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment