claude-code-teams

Use when asked to create, set up, or spin up a new agent. Covers the full lifecycle from folder creation to first message.

Contribute durable knowledge to the shared llm-wiki second brain. Use when a session produces knowledge that outlives the current project — a concept finally understood, a reusable architecture decision, a cross-project lesson, a comparison/evaluation of tools, or research findings worth keeping. Also use when the user says "add this to the wiki", "second brain", or "llm-wiki". Do NOT use for project-specific operational facts (those go to auto memory) or in-flight task state (that goes to .claude/active-task.md).

Search past Claude Code sessions across all projects on this machine. Use when the user references prior work ("like we did last week", "the bug we fixed", "what did we decide about X"), when context was compacted and details are missing, when resuming a project after time away, or before re-deriving a solution that may already exist in a past session. Keyword FTS5 search over full transcripts including tool output.

Use when asked to create, update, delete, or reconcile a calendar invite. Covers the draft-first approval flow, attendee lookup, timezone rules, and duplicate reconciliation.

Use when asked to write, reply to, forward, or send an email on the principal's behalf. Covers the draft-first approval flow, voice rules, and account selection.