Insights

Review the current conversation's failures, successes, and learnings. Compile them into proposed CLAUDE.md updates.

Steps

1. Scan the current conversation for:

   • Scripts that failed and were fixed (what broke, what fixed it)
   • New patterns discovered (API quirks, timing, edge cases)
   • New tools/scripts created
   • Preferences expressed by the user
   • Anything that cost tokens that could be avoided next time

2. Draft updates in two buckets:

   Local (project CLAUDE.md):

   • New entries for the failure/success log
   • New scripts or skills to document
   • Project map updates

   Global (GLOBAL_CLAUDE.md):

   • Recurring patterns across projects
   • New preferences or conventions
   • Token conservation lessons

3. Present both drafts to the user as a table: | Scope | Section | Proposed Addition |

4. WAIT for user approval before writing anything. Never update GLOBAL_CLAUDE.md without explicit confirmation.