Reflect
Review the current conversation and suggest high-ROI improvements. Keep suggestions brief and actionable.
What to Look For
- •
CLAUDE.md updates — Did you make a mistake that better guidance would prevent? Did the user correct you on a pattern or preference? Did you learn something about the codebase that would save time next session? Did anything in the conversation contradict or conflict with existing CLAUDE.md guidance (stale rules, outdated patterns, wrong assumptions)?
- •
Wallet documentation sync — Did the conversation change any behavior documented in the
agicash-wallet-documentationskill? Read its SKILL.md to understand what it covers, then selectively check only the reference files relevant to the changes made. Suggest edits if anything is now out of date. - •
Skill improvements — Did you use a skill that gave bad advice, was missing context, or had an awkward workflow? Would small edits make it more effective?
- •
New skills — Did the conversation involve a repeatable workflow that would benefit from a skill? Only suggest if it came up naturally and seems like it would be used again.
Workflow
- •Review the conversation history
- •For each category above, note anything worth capturing
- •For wallet documentation sync: read the SKILL.md overview, then only read references that overlap with the changes made in this conversation (e.g., if you changed the send flow, read
cashu-lightning-send.md— don't readspark-operations.md) - •Present a short numbered list of suggestions with a one-line rationale each
- •Ask the user which (if any) they want to act on
- •Based on their response, invoke the appropriate skill (
/update-context,/skill-creator, or edit the skill/documentation directly)
Guidelines
- •Suggest 1-3 items max. If nothing is worth capturing, say so.
- •Prefer updating existing context over creating new things
- •Don't suggest things already covered in CLAUDE.md
- •Be specific: "Add to CLAUDE.md that X" not "Maybe update docs"