Claude Code✓ Confirmed in official docsOct 1
Have Claude read your last 20 session logs and turn what you keep asking into mods
Claude Code keeps every session as .jsonl under ~/.claude/projects/<project>/. What you ask over and over, and which commands you cancelled halfway, are all in there. Read that before copying the example mods, and the mods you actually need fall out.
Read https://claude.dev/blog/getting-started-with-claude-code-mods/ first.
Then go through my last 20 sessions in ~/.claude/projects/ for this project and find three kinds of things worth turning into a mod:
1. Questions or requests I repeat across sessions, with counts and my exact words.
2. Commands I stopped partway, rejected, or asked you to undo.
3. How I check your changes (listing files, pasting diffs, asking for explanations).
For each idea: a name, my quoted words, and a few "what it should show" lines. If a status line or a setting already covers it, say so. Rank by usefulness. Show the ideas first, don't build anything yet.
Those log files hold your prompts and file contents verbatim, so on a shared machine read the security tip below first.
Get notified when a new tip lands
Tip alerts only go out in the app. Install it and turn notifications on.