team-memory

name	team-memory
description	Store, search, and manage team memory from AI coding sessions. Use /remember to save observations (conventions, gotchas, debugging tips, architecture decisions, workflows). Use /recall to search memories by semantic query. Use /feedback to rate memory quality (helpful/harmful/irrelevant). Triggers on any request to save, recall, search, or rate team knowledge.

Team Memory

Manage a shared team memory system backed by a Cloudflare Worker with semantic search.

Commands

/remember — Store an observation

Save a new observation to team memory.

TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/remember.ts "<observation text>" [--category=<category>] [--priority=<priority>]

Categories: convention, gotcha, debugging, architecture, workflow Priorities: critical, moderate, ephemeral

Defaults: category=convention, priority=moderate

Examples:

TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/remember.ts "PlanetScale returns strings for COUNT columns — always wrap with Number()" --category=gotcha --priority=critical
TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/remember.ts "Use ULID for ID generation, not CUID2" --category=convention

/recall — Search memories

Search team memory by semantic query.

TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/recall.ts "<query>" [--limit=<n>] [--category=<category>] [--priority=<priority>]

Default limit: 5. Results are ranked by relevance.

Examples:

TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/recall.ts "database migration patterns"
TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/recall.ts "Stripe" --category=gotcha --limit=10

/feedback — Rate a memory

Provide feedback on a memory's usefulness.

TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/feedback.ts <observation-id> <signal> [--note="<reason>"]

Signals: helpful, harmful, irrelevant

Examples:

TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/feedback.ts 01J5K3M2N7 helpful --note="Saved me from a production bug"
TEAM_MEMORY_URL=https://team-memory.zacjones93.workers.dev bun run .claude/skills/team-memory/scripts/feedback.ts 01J5K3M2N7 irrelevant

Environment

Production URL: https://team-memory.zacjones93.workers.dev

All commands below include the env var inline. If TEAM_MEMORY_URL is already set in your shell, the prefix is optional.

Hooks

• SessionStart: Reminds the agent about the memory system and how to use /recall for task-relevant lookups
• SessionEnd: Reads transcript JSONL, extracts user/assistant messages, POSTs to /sessions
• Export: Syncs memories to MEMORY.md between <!-- BEGIN TEAM-MEMORY --> / <!-- END TEAM-MEMORY --> markers