Tip

Run: bash "$(cat ~/.claude/respect/plugin_root)/scripts/tip.sh" <size> [N for custom] [summarized reason]

• Pass the tip size, number (if custom), AND the SHORT summarized reason
• The script stores the summary in wallet history for tracking

If script exited non-zero: relay the error message to the user, stop

Parse the structured KEY=VALUE result and respond conversationally

Write to auto-memory (durable learning):

• Read current respect-feedback.md from the auto-memory directory for the current working directory
  • Memory dir: ~/.claude/projects/[ENCODED_CWD]/memory/ where ENCODED_CWD = CWD with / and . replaced by -
• If structured learning was extracted, add under "## Learnings" section:

  ### YYYY-MM-DD | [Summary] (+N)
  **Lesson:** [What to do in the future]
  **Context:** [When this applies]
  **Why:** [Reasoning behind the approach]
  **Session:** N
  

• If simple tip (no learning), add under "## What I Did Well" section:

  - ✅ [summary] (+N pts, session S)
  

• Keep file concise: if "## Learnings" exceeds 20 entries, remove oldest
• If "## What I Did Well" exceeds 30 entries, remove oldest
• This creates persistent, actionable memory across sessions

Determine learning scope (cross-project or local):

• For each structured learning, decide if it is global or local:
  • Global — lesson applies regardless of project. Examples:
    • Environment/OS: "don't use timeout on macOS"
    • Universal practices: "run tests before claiming done"
    • Tool-agnostic habits: "don't hardcode secrets"
    • Workflow patterns: "push repo before bumping version"
  • Local — lesson is specific to this codebase. Examples:
    • "use the v2 API for this service"
    • "run make integration-test not make test in this repo"
    • "config lives in src/config/ not project root"
• If global, also append the learning to ~/.claude/respect/global-feedback.md
  • If the file doesn't exist, create it with:

    # Global Respect Feedback
    
    Learnings that apply across all projects.
    
    ## Learnings
    
    ## Mistakes to Avoid
    

  • Add under the ## Learnings section using the same format
  • Keep the global file concise: max 30 entries under ## Learnings, remove oldest if exceeded
• Simple tips (no structured learning) are always local only
• When writing globally, tell the user: "This learning applies globally across all projects."