claude-code-tips

See active Claude Code sessions on this machine and coordinate across them via direct messages, status announcements, and file-overlap awareness. Triggers when the user asks "who else is running?", "any other claude open?", "what other sessions are active?", "tell <name> to ...", "ping <peer>", "let peers know I'm doing X", "broadcast <status>", "check the cc digest", or any cross-session / multi-agent coordination on this machine.

measure your real CC throughput against the time rule's matrix, using lore.db

export the lore knowledge graph or its slices to json, csv, or markdown

explore relationships in the lore knowledge graph - cooccurring files, project sessions, sibling sessions, tagged notes

query the lore knowledge graph for sessions, costs, tools, projects, search, and patterns

capture decisions, lessons, reminders, and todos into the lore knowledge graph

walk the user through a low/medium/high effort A/B/C throughput benchmark on their current model

estimate CC active time for a task using the time rule, with dynamic effort resolution

all /lore intents, examples, and setup